Readers Insights and Feedback: Dealing with Record Locks
July 17, 2002 Timothy Prickett Morgan
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