Re: logging lock-wait conditions -- MIDRANGE-L

Subject: Re: logging lock-wait conditions
From: Jerry Draper <midrangel@xxxxxxxxxxxxx>
Date: Thu, 29 Dec 2016 16:18:37 -0800
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>

I think the lock is coming from existing use of a master file by local IBM I users.

It looks like the exit pgm would work for opening files for the first time.

J

On 12/29/2016 12:48 PM, David Gibbs wrote:

On 12/29/2016 2:30 PM, Jerry Draper wrote:

We have a need to log lock-wait conditions on a couple of files .

How might this be accomplished?

Existing IBM I cmds?

I've never tried this before ... but there is a Open Database File exit
program that you might be able to use.

http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_61/apis/xopendbf.htm

I'm thinking you could hook into the exit point and, before the database
file is opened, try to get a non-exclusive lock. If it fails, log it
and continue.

david

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.