Detecting Record Locks (AREV Specific)
At 14 JUN 2004 10:04:54AM Clay Borne wrote:
I've been working on a process that would detect who is locking a particular record. I've been trying to use the mfs. I tried putting the code in the READ.RECORD section. However, I am having problems with it detecting the key being accessed, I don't think the record has become the @RECORD at this point. I also tried putting the code in the LOCK.RECORD section, that too gave me grief. Does anyone have any ideas on this? It is a simple procedure that just gets the key of the @record, the username, and date time and writes it to table. Your thoughts would be appreciated.
At 14 JUN 2004 10:09AM [email protected] wrote:
Well putting it in the lock.record section stands a better chance of working than putting it in the read.record section. However these is also the issue of local lock tables to contend with. What was the problem with Lock.Record?
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 14 JUN 2004 10:31AM [email protected] wrote:
Clay,
The LOCK.RECORD sub *is* the place to put it. What happens to make this not viable.
Since this is 'Arev Specific' i can assume you are using Arev? (sometimes this doesn't seem to be the case
. Also what version of the MFS shell are you using?
[email protected] onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"
David Tod Sigafoos ~ SigSolutions
At 14 JUN 2004 02:02PM [email protected] wrote:
Sorry the last post was so short ..
As mentioned the LOCK.RECORD should be what you use.
As for your problem with the READ.RECORD
]] I've been working on a process that would detect who is locking a particular record. I've been trying to use the mfs. I tried putting the code in the READ.RECORD section. However, I am having problems with it detecting the key being accessed, I don't think the record has become the @RECORD at this point
You are correct about @RECORD. here is what the MFS should be showing you.
On coming into the mfs for READ (or reado) you should have the following:
CODE =1 (2 for reado)
BFS =MFSNAME@vmRTP57
HANDLE =00000000011volume\rev10001.lk
NAME =id (id of what you are reading)
FMC =unassigned
RECORD =null
STATUS =unassigned
after the NEXTFS call you should have something like
CODE =1 (2 for reado)
BFS =MFSNAME@vmRTP57
HANDLE =00000000011volume\rev10001.lk
NAME =id (id of what you are reading)
FMC =unassigned
RECORD =full contents of record being read
STATUS =1 (if read was okay)
I have a little routine which will display the values at all times in a mfs if you want it
[email protected] onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"
David Tod Sigafoos ~ SigSolutions
At 14 JUN 2004 06:50PM [email protected] wrote:
opps .. forgot to mention you can get the mfs a href=ftp://ftp.sigafoos.org]here[/url]
It is in dos format so to get into Arev ..
COPY DOS 'where_you_put_it\dsigmfs.mv (R) TO:(BP DSIGMFS
then compile and use as you want. It does post a message for every even in the mfs .. just a warning
[email protected] onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"
David Tod Sigafoos ~ SigSolutions
At 16 JUN 2004 11:00AM Clay Borne wrote:
Thanks for all the help!
At 16 JUN 2004 01:12PM [email protected] wrote:
So, did you get the mfs to trap delete as needed?
[email protected] onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"
David Tod Sigafoos ~ SigSolutions
At 24 JUN 2004 06:07PM thingy wrote:
I just write a 40 line program which lists all locks and who has them.
Got the idea from NLM_STATS.