Unlock All (AREV Specific)
At 25 SEP 1998 01:49:11PM Victor Engel wrote:
I was just working on a routine to detect multiple concurrent sessions using locks and am being foiled by the logon process. I'm using HR-1 5.5 (Arev 3.02). I put the code in the VOC item that is executed automatically by the system on logon. My plan was to set a lock that would remain throughout the session. Problem is, the logon process seems to do an unlock all. What is it that is doing this unlock all? How can I hook into the logon process after the last unlock all?
At 25 SEP 1998 06:27PM Jonathan Bird wrote:
I've hit this problem too.
I set a lock on a user record in a table. It seems to hold a file lock, but loose the record lock. The only way around it was to open the file again and immediatly place the lock on the record. It seemed to work then, but odd. eh??
At 25 SEP 1998 09:19PM Steve Smith wrote:
I suspect that either DICT.MFS or indexing does "unlock all"s. I understand there is a certain call to made to the BFS which you might intercept, via MFS, to reinstate your lock after an unlock all.
Steve
At 28 SEP 1998 09:42AM Victor Engel wrote:
It is RTP2 that is doing it. The question is, how can I load a process immediately after RTP2 is finished?
At 28 SEP 1998 12:10PM Andrew P McAuley wrote:
Well MFSs are called on install, so you could write an MFS just for this….
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 28 SEP 1998 02:57PM Victor Engel wrote:
I was hoping not to have to go the MFS route. I hate to clutter up the system with unnecessary MFSs since they are all executed for certain operations, such as UNLOCK ALL.
At 28 SEP 1998 05:25PM Aaron Kaplan wrote:
If memory serves, there were all sorts of things relating to unlock all and transactions, so it could be possible to create some sort of transaction record in your logon that would prevent the unlock all call.
akaplan@sprezzatura.com
