Looks like your copyright protection filter prevented you from posting
code but your netiquette protection software missed the huge
unnecessary quote. ;)
BTW, if you do publish that code, its copyright is no longer valid.
You can't publish helpful code to a forum with a copyright that tells
people
te: Tue, 27 Mar 2012 15:30:09 -0400
From: Rex Gozar
To: dgr...@dagconsulting.com, U2 Users List
Subject: Re: [U2] Detecting idle time in INPUT statement.
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
It does not matter if a system is old or not, you gotta keep
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Don Robinson
Sent: Tuesday, March 27, 2012 6:27 AM
To: U2 listserver
Subject: [U2] Detecting idle time in INPUT statement.
Hello all,
We are running Universe 10.1 on AIX with about 500 users. We have a problem
with users opening up a
pm
Subject: Re: [U2] Detecting idle time in INPUT statement.
Wj,
ou are right, I'm a hired gun and try to do what the *boss* wants.
As far as adding LOCKED clauses, that would only solve a part of it. The second
ser would know why they can't update a record but would still have to call
If anyone DOES want the equivalent of Unidata's INPUT... WAITING for Universe...
http://www.pickwiki.com/cgi-bin/wiki.pl?InputWait
Regards, Keith
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-user
educe user aggravation and calls to the support group.
We shall see how the time out thing work outs.
Thnaks,
Don Robinson
From: Wjhonson
To: u2-users@listserver.u2ug.org; dgr...@dagconsulting.com
Sent: Tuesday, March 27, 2012 3:37 PM
Subject: Re: [U2] Detecting idle time in INPUT statement.
;* Do whatever you want here.
END ELSE
*
* User entered something, proceed as usual.
*
CRT
CRT 'User entered: ': ZZ
END
*
STOP
END
Thanks,
Don Robinson
From: David A. Green
To: 'Don Robinson' ; 'U2 Users List'
Sent: Tuesday, March 27, 2012 2:31 PM
Subject: RE: [
He already has the use-case; someone in some specific screen/program
is getting locked out. That's where you start.
On Tue, Mar 27, 2012 at 3:54 PM, George Gallen wrote:
> The tough part isn't so much the qty of but knowing which ones are the
> important
> Ones that will most likely be affected
n the dark.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rex Gozar
Sent: Tuesday, March 27, 2012 3:46 PM
To: U2 Users List
Subject: Re: [U2] Detecting idle time in INPUT statement.
The OP's system probably do
List
Sent: Tue, Mar 27, 2012 12:46 pm
Subject: Re: [U2] Detecting idle time in INPUT statement.
The OP's system probably doesn't have three thousand READU statements;
'm willing to guess a few hundred. And out of that few hundred,
aybe a dozen of those READU's block user a
The OP's system probably doesn't have three thousand READU statements;
I'm willing to guess a few hundred. And out of that few hundred,
maybe a dozen of those READU's block user access during normal
day-to-day operation. And yet a CEO, manager, whatever wouldn't have
a problem implementing some i
Tue, Mar 27, 2012 12:30 pm
Subject: Re: [U2] Detecting idle time in INPUT statement.
It does not matter if a system is old or not, you gotta keep it up to
ate. "Maintenance programming" means adding LOCKED clauses that
hould have been there in the first place. I doubt it would take more
It does not matter if a system is old or not, you gotta keep it up to
date. "Maintenance programming" means adding LOCKED clauses that
should have been there in the first place. I doubt it would take more
than a few hours; probably less time than writing and debugging some
off-the-wall input time
(480) 813-1725
DAG Consulting
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Don Robinson
Sent: Tuesday, March 27, 2012 11:07 AM
To: U2 Users List
Subject: Re: [U2] Detecting idle time in INPUT statement.
Thanks to
outside and whack the mole when it appears.
-Original Message-
From: Rex Gozar
To: U2 Users List
Sent: Tue, Mar 27, 2012 11:24 am
Subject: Re: [U2] Detecting idle time in INPUT statement.
I know the OP wanted to know how long a user session has been idle,
ut real problem is the second
I know the OP wanted to know how long a user session has been idle,
but real problem is the second person waiting for the lock to be
released.
The best practice is to always have LOCKED clauses on your READU's,
and never to "block on a lock", i.e. a user input process should hit
the locked clause
Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Don Robinson
Sent: Tuesday, March 27, 2012 2:07 PM
To: U2 Users List
Subject: Re: [U2] Detecting idle time in INPUT statement.
Thanks to all who responded.
At the point in the programs
al Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Don Robinson
Sent: Tuesday, March 27, 2012 6:27 AM
To: U2 listserver
Subject: [U2] Detecting idle time in INPUT statement.
Hello all,
We are running Universe 10.1 on AIX with about 500 users. We
From: Wjhonson
To: u2-users@listserver.u2ug.org
Sent: Tuesday, March 27, 2012 1:53 PM
Subject: Re: [U2] Detecting idle time in INPUT statement.
Right, you don't care if they are at input exactly.
You care if they are squatting on a lock.
So your periodic lock checker thingie, has to be c
List
Sent: Tue, Mar 27, 2012 10:44 am
Subject: Re: [U2] Detecting idle time in INPUT statement.
I guess you would need to merge this with the routine to detect who has locks
pen (except running every two mins, not five)
To determine who is sitting at an input prompt at a menu (which might be ok
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Tuesday, March 27, 2012 12:18 PM
To: donr_w...@yahoo.com; u2-users@listserver.u2ug.org
Subject: Re: [U2] Detecting idle time in INPUT statement.
*Timed* activity
obinson
To: U2 listserver
Sent: Tue, Mar 27, 2012 6:26 am
Subject: [U2] Detecting idle time in INPUT statement.
Hello all,
e are running Universe 10.1 on AIX with about 500 users. We have a problem with
sers opening up a record which puts a lock on it and just letting it sit at the
NPUT state
-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Don Robinson
Sent: Tuesday, March 27, 2012 6:27 AM
To: U2 listserver
Subject: [U2] Detecting idle time in INPUT statement.
Hello all,
We are running Universe 10.1 on AIX with about 500 users. We have a
e out condition.
The VAR = '*' is our exit character.
Rich
- Original Message -
From: "Don Robinson"
To: "U2 listserver"
Sent: Tuesday, March 27, 2012 9:26:38 AM
Subject: [U2] Detecting idle time in INPUT statement.
Hello all,
We are running Univers
Its strange to me that Universe does not have this feature built in to the
INPUT statement...
Something like:
INPUT user_input TIMEOUT 30
Maybe I have missed something in the UV docs, but, I never could find
anything built in. If I remember correctly other flavors of MV have had
this for a whil
Check INPUTIF, this will return a value if the input buffer has
something. If after 2 minutes of checking INPUTIF you have nothing it's
because the user isn't active. If you do a LOOP with INPUTIF inside be
careful to put an RQM or something similar in the loop.
On Tue, 27 Mar 2012 06:26:38 -0
Hello all,
We are running Universe 10.1 on AIX with about 500 users. We have a problem
with users opening up a record which puts a lock on it and just letting it sit
at the INPUT statement for a long time.
Most of the locking within the application does not use the LOCKED clause so
when a se
27 matches
Mail list logo
