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
ously 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
To: u2-users@listserver.u2ug.org
Sent: Friday, March 20, 2009 6:09:46 PM
Subject: Re: [U2] [UV] Config parameter fo
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 i
@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
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
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
