Like Mike said, you want to use LIST.READU (or LIST.QUEUE) to see the
locks. However, UniData, unlike UniVerse does have the file name and not
just the number.

The Status() after a readu gives you the UID (pid) of the process that
has the record locked. You can parse it out of the array returned with
GETREADU(). This is like capturing the LIST.READU output. You can get
the user

You may also find RECORDLOCKED handy.

The TCL HELP should give you what you need for these.

Hth
Colin Alfke
Calgary - I can't believe it snowed this morning - Canada

>-----Original Message-----
>From: Susan Joslyn
>
>Hello wizards,
>
>I've read what I can find on the subject, but I'm not finding 
>what I need.
>As usual, anyone who knows where the info is, I would not be 
>the least bit offended if you just point.  Or if you know off-hand ...
>
>(Presently grappling with Unidata):
>
>When I hit a lock with a:
>READU this FROM that,ID LOCKED locked clause ELSE whatever 
>
>LIST.LOCKS from TCL has always been worse than useless for me. 
> For example at this exact moment I'm holding locks on 3 
>sessions, yet if I run LIST.LOCKS on a 4th session it displays 
>ABSOLUTELY NOTHING.  
>
>I don't see much on offer in the LOCKED clause, although the 
>online help suggests that STATUS() will return the user number 
>of the lock it ran into.
>Can't understand its output... I have a very short program 
>that displays STATUS(), opens the file and displays STATUS() 
>then does a READU against an item I purposefully have locked 
>on another session and I display STATUS()  a third time.  What 
>do you suppose its giving me, and what can I do with it?
>
>1 STATUS = 0     <-- beginning of program
>2 STATUS = 1     <-- after the open
>3 STATUS = 197613 <-- this is what it gives me after the READU 
>against a locked item
>
>What I want to do is determine who/what has the lock, tell the 
>user, I also want to be able to carry on under my own 
>conditions when ud 46 flag is set which will by default allow 
>edits to items I've locked against my own session.  Which is 
>too loose -- I want to check to make sure I'm in the exact 
>right condition to do that and I'm not sure how I can (by 
>seeing what is holding the lock) but ... does anyone know how 
>to get ANY information out of a lock?
>
>Susan
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/

Reply via email to