Oops! Not VPYLIB - CPYLIB - the keyboard moved on me!

On 8/6/2015 9:05 AM, Vernon Hamberg wrote:
A library is essentially only a list of the objects it contains. I expect that the only time I'd get a lock on a library is if I'm doing something with it directly, like being in a library list or VPYLIB kind of thing. I even tried DSPLIB and WRKLIB - once the list of objects was displayed for DSPLIB, there was no lock on the library. WRKLIB just listed the library name at first, no lock then, either.

On 8/6/2015 8:39 AM, John McKee wrote:
My guess is that command is working correctly. No locks on the library
itself. Why would a lock on an object in a library also lock the library?
Or, I am wondering, if there might be a specific type of lock on the
library, such as SHRRD that might be related to an open file in the library.

John McKee

This thread ...


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

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