RE: backup causing 30000 locks?? -- 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: backup causing 30000 locks??
From: "Richard B Baird" <rbaird@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 28 Nov 2001 10:53:50 -0500
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/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-Unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

all,

no luck on finding the reason for the 30000 locks on the backup.
I'm not actually on the machine - this is all second hand:

no files with a lot of members. (at lease none in *USRLIBs)
no Lansa
prechk(*no)
Approx 5000 physical files in *USRLIBs. (quite a few, but still, not
uncommon)

As Jim said, it's probably normal and I'm inclined to leave it go.   Thanks
to all for your help!

Rick

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: backup causing 30000 locks?? , Eric Lehti

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.