Hi, David:

Since at least V5R2, (maybe V5R1) and above, we have the system value QLIBLCKLVL that can be set to 0 or 1:

1=Lock libraries in the library search list (the default, for compatibility with previous releases)

0=Do not lock libraries in the library search list

You can change this system value, and then, after the next IPL, no libraries (*LIB) will be locked unless you explicitly lock them (e.g. by issuing an ALCOBJ for that library). Changing this system value "on the fly" will not affect jobs already in progress, such as system jobs like QSYSARB ...

Hope that helps,

Mark S. Waterbury

> On 11/17/2011 10:33 AM, David Gibbs wrote:
On 11/17/2011 9:02 AM, Richard Reeve wrote:
Does anyone have a good explanation of the ramifications and possibly
the why's and why nots of placing user libraries in the system
portion of the library list? I just signed on to a client box and
noticed many user libraries in the system portion of the list. While
it looked odd, I don't know enough about it to say that it's a bad
(or possibly a good) practice.
One thing to keep in mind with libraries in the system library list ... they are locked by EVERY job in the system ... so renaming or deleting it is going to be very difficult.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.