Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!safn2!rey
From: rey@safn2.UUCP (rey)
Newsgroups: comp.databases
Subject: rlock() in SCO foxbase+.
Keywords: foxbase, rlock
Message-ID: <553@safn2.UUCP>
Date: 23 Sep 90 19:18:48 GMT
Organization: Southern Aluminum Finishing, Atlanta, GA
Lines: 26

Set up is SCO Unix 3.2.2 on Compaq 386. SCO Foxbase+.

Could some one please explain rlock() in foxbase+. I am converting 
Dbase single user programs.

Who owns the lock? (Same question as who can write to an rlocked record.)
	a) The foxbase procedure that called rlock() sucessfully.
	b) The work area that called rlock() sucessfully.
	c) The process (pid).
	d) The user (uid).
	e) The tty?

I think the answer is a). When I rlock() then call another
	procedure I cannot append. But that doesn't seem correct design.

My Dbase IV guide talks about rlock() being cumlative up to 50 locks.
	On the same record? Can only 50 different records be locked?

How are the locks implemented? Are they in the .dbf file header or
	in the record being locked or in shared memory (Which I
	don't think I am using).
How about flock().
 hanks in advance.
-- 
Reynolds McClatchey (Southern Aluminum Finishing Co, Atlanta, GA, USA)
uunet!safn2!rey