Re: Finding a record lock

I'm not sure if this is too late for you but way way back
Jim Sloan built a procedure that would display a record lock.
That CLP was TAADBFFC and was issued when the program
running encountered a record lock somewhere else and then issued a message
to the offending user.
Just a thought. Again, it may be too little too late but I thought it was
an interesting
CLP when I reviewed it.

Bill





From: Brian Johnson <brian.johnson.mn@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 10/05/2016 10:11 AM
Subject: Re: Finding a record lock
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Here's an oldie that might be a good-enough alternative to custom
development:

QSYS/CHKRCDLCK



On Wed, Oct 5, 2016 at 10:00 AM, Brian Garland <brian.garland@xxxxxxxxxx>
wrote:

Thank you for all the responses.

I think at this point my only recourse is to create a tool that uses
QDBRJBRL and insert that tool into our code at key points to try to

narrow

down the location where the records locks are being left when they

should

not be.