Re: Finding a record lock

[Brian Garland <brian.garland@xxxxxxxxxx>]

Mark,

Yes, I have tried DSPRCDLCK and the QWCRLCKI api.  They do not give me the
info needed.  They just list the jobs locking the record.  I already have
that because of the error message itself has the job number.

I'm looking for something that will tell me the program so I can fix the
root cause of the problem -- bad program leaving record lock.

Brian

> Hi Brian,
> Have you looked at the DSPRCDLCK command?
> Regards,Mark.

> >    On Monday, 3 October 2016, 16:37, Brian Garland <
brian.garland@xxxxxxxxxx> wrote:

> > Is there any api or system table that would tell us the program that is
> > holding a record lock?

> > I know the job number is in the record lock message, but this is not
enough
> > info because sometimes it is a batch job that receives requests via a
data
> > queue and it potentially runs many programs and could have moved on from
> > the request that left the record lock originally.