Scott Klement wrote:

However, despite that we use QGPL this way, I still think it's the wrong thing to do. A better idea is to create your own "general purpose library" (maybe name it GENERAL or GLOBAL) and insert it into the library lists of all of the jobd's and QUSRLIBL sysval. Use that library instead. There's really no disadvantage to using your own library in this manner, and it eliminates the dangers of using QGPL.

That sparks the thought that a system value might be useful -- QourGPL (pick a name). The value would indicate which user library should be considered as the "local GPL". Third-party vendors, consultants and even in-house staff could then have a standard indication of where stuff should go that might currently get placed in QGPL.

Tom Liotta


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-2025 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.