Re: Finding a record lock -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Finding a record lock
From: MARK GOLDEN <mark_golden@xxxxxxxxxxxxxxx>
Date: Mon, 3 Oct 2016 16:41:51 +0000 (UTC)
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

This mailing list archive is Copyright 1997-2026 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.