Re: [U2] [UV] Config parameter for the READU
Back in 2002, when I wrote that, I couldn't set it to 0 and disable it. Didn't know 0 now works. Good. I usually peruse the release notes and don't recall that change. I agree, setting it to 0 to turn it off makes sense. (By the way, Mr. Fillips, Stevenson has a v in it, not a ph.) Chuck Stevenson On Fri, Mar 20, 2009 at 3:09 PM, Martin Phillips martinphill...@ladybridge.com wrote: Hi Jacques, If the value of SYSTEM(1999) is set to zero does that mean that this featured is turned off and that the READU will wait however long it takes to get the lock or does it mean it is set to the default 3600 waiting value ? Setting it to zero disables it completely. To my mind, this is the only sensible way to run but I'm open to arguments. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] Config parameter for the READU
Hi, There is a note from IBM on this: 119628. It mentions that we can't inquire as to the value of SYSTEM(1999) to know if it has been turned off or not as it will always report zero. So it looks like we will have to turn it off to make sure. It may explain some anomalies. I previously thought it was turned off because I had done a small program that would do this: CRT SYSTEM(1999) and it would print zero. - Original Message From: Martin Phillips martinphill...@ladybridge.com To: u2-users@listserver.u2ug.org Sent: Friday, March 20, 2009 6:09:46 PM Subject: Re: [U2] [UV] Config parameter for the READU Hi Jacques, If the value of SYSTEM(1999) is set to zero does that mean that this featured is turned off and that the READU will wait however long it takes to get the lock or does it mean it is set to the default 3600 waiting value ? Setting it to zero disables it completely. To my mind, this is the only sensible way to run but I'm open to arguments. Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] [UV] Config parameter for the READU
Hello, I recall reading here a while back that there is a parameter in the (possibly in the uvconfig file) that determines how long READU will wait for a lock when it is taken by someone else. Someone on the list said something to the effect that he set it to wait for one month. What is this parameter and what happens with the READU when the time set by that parameter is up ? I thought I had saved that email in my UV.KEEP folder but I can't seem to find it now. Jacques --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] Config parameter for the READU
Hi Jacques, I recall reading here a while back that there is a parameter in the (possibly in the uvconfig file) that determines how long READU will wait for a lock when it is taken by someone else. There is but it is horrendous because, when it times out, the program takes the ELSE clause so that it thinks it owns the lock. I have appended a copy of a posting from Charles Stephenson on this topic back in 2002 below. If you are looking for a simple timeout that effectively gives a delayed entry to the LOCKED clause, there is no such feature though you can manufacture it from other components. Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 = Cause: LOCK.WAIT param set to 0 instead of default 3600 (seconds) during UV.LOGIN Workaround: Set LOCK.WAIT to very large number. E.g.: ASSIGN 86400 TO SYSTEM(1999) (basic statement) SET.SQL LOCK.WAIT 86400 (tcl command) Summary: In Rev 8.3.3 UV introduced the LOCK.WAIT feature and set the default to 3600 (seconds). This parameter says that if a LOCKED clause is missing, after [LOCK.WAIT] seconds, then ignore the lock and proceed with the ELSE clause ! ? ! ? ! Until now, the workaround for this feature has been to turn off by setting the parameter to 0, typically via ASSIGN 0 TO SYSTEM(1999) typically from a program executed from UV.LOGIN, the routine in uv/VOC that everyone hits when they enter the universe shell. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] Config parameter for the READU
If the value of SYSTEM(1999) is set to zero does that mean that this featured is turned off and that the READU will wait however long it takes to get the lock or does it mean it is set to the default 3600 waiting value ? - Original Message From: Martin Phillips martinphill...@ladybridge.com To: u2-users@listserver.u2ug.org Sent: Friday, March 20, 2009 1:01:07 PM Subject: Re: [U2] [UV] Config parameter for the READU Hi Jacques, I recall reading here a while back that there is a parameter in the (possibly in the uvconfig file) that determines how long READU will wait for a lock when it is taken by someone else. There is but it is horrendous because, when it times out, the program takes the ELSE clause so that it thinks it owns the lock. I have appended a copy of a posting from Charles Stephenson on this topic back in 2002 below. If you are looking for a simple timeout that effectively gives a delayed entry to the LOCKED clause, there is no such feature though you can manufacture it from other components. Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 = Cause: LOCK.WAIT param set to 0 instead of default 3600 (seconds) during UV.LOGIN Workaround: Set LOCK.WAIT to very large number. E.g.: ASSIGN 86400 TO SYSTEM(1999) (basic statement) SET.SQL LOCK.WAIT 86400 (tcl command) Summary: In Rev 8.3.3 UV introduced the LOCK.WAIT feature and set the default to 3600 (seconds). This parameter says that if a LOCKED clause is missing, after [LOCK.WAIT] seconds, then ignore the lock and proceed with the ELSE clause ! ? ! ? ! Until now, the workaround for this feature has been to turn off by setting the parameter to 0, typically via ASSIGN 0 TO SYSTEM(1999) typically from a program executed from UV.LOGIN, the routine in uv/VOC that everyone hits when they enter the universe shell. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
