] RECORDLOCKED statement
Assign the result to a variable: that reduces the i/o to the lock manager by
60%+
Brad
This communication, its contents and any file attachments transmitted with it
are intended solely for the addressee(s) and may contain confidential
proprietary information.
Access by any
t: Re: [U2] RECORDLOCKED statement
The other consideration is that each case statement uses the same
RECORDLOCKED(PICH.TX, SO) function reference, meaning it runs the function 3
times (according to your snippet).
I would normally assign the function result to a variable and test the
variable i
aul_doming...@neimanmarcus.com
Sent: Tuesday, December 15, 2009 5:27 PM
To: U2 Users List
Subject: Re: [U2] RECORDLOCKED statement
The only consideration is that your second case statement picks up at -2
instead of -1.
I think you are going for
CASE RECORDLOCKED(PICH.TX, SO) <= LOCK$OTHER.READL which is the -1
Assign the result to a variable: that reduces the i/o to the lock manager by
60%+
Brad
- Original Message -
From: "Gregor Scott"
To: "'U2 Users List'"
Sent: Tuesday, December 15, 2009 8:39 PM
Subject: Re: [U2] RECORDLOCKED statement
The other c
List
Subject: Re: [U2] RECORDLOCKED statement
The only consideration is that your second case statement picks up at -2
instead of -1.
I think you are going for
CASE RECORDLOCKED(PICH.TX, SO) <= LOCK$OTHER.READL which is the -1 return
value. At least according to the UniVerse documentat
ing...@neimanmarcus.com
972-401-6502
Baker Hughes
Sent by: u2-users-boun...@listserver.u2ug.org
12/15/2009 05:17 PM
Please respond to
U2 Users List
To
'U2 Users List'
cc
Subject
[U2] RECORDLOCKED statement
I admit I have never used this little jewel of a [UV] statement, so
although
I admit I have never used this little jewel of a [UV] statement, so although
the code runs and works as designed, before I load it to production, someone
please tell me if there are any nuances that would improve the design/operation.
CASE RECORDLOCKED(PICH.TX, SO) >= LOCK$MY.READU
* This
