Although you are right in a grounds-up approach, the problem is that, most code is old. Many managers are adverse to *fixing* code that is working, because if you keep opening the oven door the souffle will fall. Even if you just stomp around a lot....
So the approach of monitor from the outside and whack the mole when it appears. -----Original Message----- From: Rex Gozar <[email protected]> To: U2 Users List <[email protected]> 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 person waiting for the lock to be eleased. The best practice is to always have LOCKED clauses on your READU's, nd never to "block on a lock", i.e. a user input process should hit he locked clause and report who has the desired record locked, and iving the user an out if they cannot access the record at this time. atch and phantom processes should not block either, waiting 5-10 econds and retrying up to specific number of times (say 10), then kipping over the record and leaving it for subsequent processing. rex ______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
