Readers Insights and Feedback: Dealing with Record Locks
July 17, 2002 Timothy Prickett Morgan
Hey, Ted:
It’s been over a year, but I had a batch job that would run into a record lock problem . If it encountered a record lock, it would retrieve the job name and send a break message to that device (all problems were caused by interactive jobs) asking the user to release the record being updated (back out of the update screen).
|
Also, I modified update programs and screen files to use the INVITE keyword, and I set the device wait to three minutes; if the user had the update screen up for over three minutes, the RPG program would detect the wait expiration and release the record that was locked for update, in addition to backing out of the update screen. Typically people would call an update screen and then leave for lunch; this would cancel their update screen, and they would resume when returning from lunch. It seemed to have solved our problem.
— Mike
Sponsored By ADVANCED SYSTEMS CONCEPTS |
SEQUEL meets all your iSeries and AS/400 data access needs in a single, integrated solution:
Take 6 minutes to view a SEQUEL ViewPoint ScreenCam movie to see how simple Windows-based AS/400 and iSeries data access can be! In just a few short minutes, you can find out ways to make your job easier and improve data access throughout your organization. Download the ViewPoint movie here . For more information or a FREE trial of SEQUEL, call 847/605-1311 or visit Advanced Systems Concepts. |