The only solution I have ever found is to find the program(s) that get a
record for update followed by an EXFMT and change that process so that
getting the record is a read-only, no lock.
Then, when that user gets back from lunch and presses the Enter key, do
another read(locked), and update. Also, don't forget to check to see if
another user has changed the data in the meantime. "Last one wins" is a
tough glitch to find and fix two years from now.
On 12/16/2015 8:37 AM, Werner, Robert wrote:
I've changed my job to DFTWAIT(1) yet when I run a program it hangs on a "chain(e)" statement if I have that specific record locked on another session. We are on v7r1 tr9.
RPG Programmer, Systems Development | TUI Marine
93 N. Park Place Blvd , Clearwater FL 33759-3917
T: +1 727 614 7302 | Robert.Werner@xxxxxxxxxxxxx<mailto:Robert.Werner@xxxxxxxxxxxxx>
P Please consider the environment - do you really need to print this email?
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact