RE: Determining Lock on Specific PF Record -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Determining Lock on Specific PF Record
From: "Barton, Mike" <Mike.Barton@xxxxxxxxxxxxx>
Date: Wed, 11 Jan 2006 16:20:20 +0100
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

>Is there an easy way to determine who has a lock on a specific record
(or >set of records) in a Physical File?  We have a problem in one of
our >records where when we try to update it the system tells me that it
is >unable to allocate a record in the PF.  However, there are other
users who >are currently updating other records in the same PF without
issues.

try the DSPRCDLCK {file name} command

Mike

--

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.