Think LIST.READU is what you are looking for. LIST.LOCKS only displays the
64 semaphore locks which I don't think are too common anymore.
Trick with LIST.READU was equating the file number to the proper data file
if you were doing it programmatically.
-Original Message-
From: [EMAIL
On Universe LIST.LOCKS shows task locks (i.e. LOCK 5 in UVBASIC )- I
have to use LIST.READU EVERY to get readu locks. Does UniData have a
LIST.READU command?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn
Sent: Thursday, April 14, 2005
other resources include:
LIST.QUEUE and related GETQUEUE() UniBasic function - both show users
queued up for a lock (those users would not be using the LOCKED clause).
LIST.READU (noted) and GETREADU() function.
Don't forget the DETAIL keyword on LIST.READU and LIST.QUEUE to show full
data - not
Susan,
I think what you're looking for is LIST.READU and / or LIST.READU DETAIL.
HTH
Mark
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Susan Joslyn
Sent: Thursday, April 14, 2005 7:33 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Locks,
LIST.READU DETAIL
[EMAIL PROTECTED] 4/14/05 10:47:31 AM
Think LIST.READU is what you are looking for. LIST.LOCKS only displays the
64 semaphore locks which I don't think are too common anymore.
Trick with LIST.READU was equating the file number to the proper data file
if you were doing it
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
Ooops, I thing I forgot to mention. On some versions of UniData (5.2.4?)
doing a /TCL in SB+ will cause UniData to not output information with
LIST.READU. I don't recall if there is also a problem with GETREADU() -
plus it's already in an array so you don't have to trim and parse
(truncated) data
Subject: Re: [U2] Locks, releases and STATU() (oh my)
Is that DETAIL keyword for LIST.READU just for Unidata? Doesn't seem
to
work on Universe.
-Dianne
Wally Terhune wrote:
other resources include:
LIST.QUEUE and related GETQUEUE() UniBasic function - both show users
queued up for a lock
, releases and STATU() (oh my)
Ooops, I thing I forgot to mention. On some versions of UniData
(5.2.4?) doing a /TCL in SB+ will cause UniData to not output
information with LIST.READU. I don't recall if there is also a problem
with GETREADU() - plus it's already in an array so you don't have to
trim
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Locks, releases and STATU() (oh my)
Is that DETAIL keyword for LIST.READU just for Unidata? Doesn't seem
to
work on Universe.
-Dianne
Wally Terhune wrote:
other resources include:
LIST.QUEUE and related GETQUEUE() UniBasic
10 matches
Mail list logo
