This still would not be accurate for the reasons already stated.
The call stack only shows you what routine is on the stack.  If the lock had 
been set for hours, who knows what routine was there previously?
As you yourself stated, locks can persist, after the routine which created them 
has gone away.

The only viable solution is to record the lock at the time it is set.

-----Original Message-----
From: George Hammerle <>
To: u2-users <>
Sent: Thu, Sep 8, 2011 12:36 pm
Subject: Re: [U2] Lock Status

ven if the program ended that locked the item, the lock could still be 
aintained if the file variable was passed.
I know this is after the fact but, one option going forward would be to write a 
rapper program for READU's and call it "LOCK.RECORD". I use this approach 
1. If it is a phantom, perform a READU
. If it is a real user, use the LOCKED clause 
a. If it is locked, display whom has it locked followed by an INPUT ( if it is 
B+, use a DISP ).
b. If it is not locked, lock it.
 This allows them to see who has them locked and contact the guilty party
. NEW OPTION : Once locked, you could get the call stack and record to a file 
hich program locked it ( excluding this sub - LOCK.RECORD ). Or you could add 
n additional parameter to this sub and pass in the program name. 

e already do 1 and 2, but 3 would be an interesting option. 

e also have a sub called LOCK.RECORD.ESCAPE that gives the user the option to 
scape if the record is locked and it also displays who has them locked. We only 
se this option when it is safe to escape and it sends back "ESCAPED" 1 or 0 so 
e can handle the escape properly.

This e-mail and any files transmitted with it are confidential and intended
olely for the use of the individual or company to whom they are addressed. If
ou have received this e-mail in error, please notify the sender immediately and
elete this e-mail including all attachments from your system. Thank you
2-Users mailing list

U2-Users mailing list

Reply via email to