×
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.
With V5R3M0 and above, we have the system value QLIBLCKLVL that can be
set to 0 to inhibit the *SHRRD lock on *LIB objects that are added to
each job's library list. This is convenient when we need to be able to
rename a library (for example, on a test system).
Last week, I was working with a customer running V6R1, and they changed
QLIBLCKLVL from 1 to 0, but the next day, there were still a large
number of system jobs (spool jobs, etc.) that held a *SHRRD lock on the
library in question, presumably because those jobs started before they
changed QLIBLCKLVL.
They decided to wait for the next scheduled IPL of the system over the
week-end. Now, I see the QSYSARB job holds a *SHRRD lock on several
libraries, including the one we want to rename.
Does anyone know what is going on here?
Under what conditions does QSYSARB hold a *SHRRD lock on a library, and
why does it appear not to honor the QLIBLCKLVL system value?
Thanks,
Mark S. Waterbury
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.
midrange.com
