>At 08:47 AM 12/9/97 -0600, you wrote:
>>>  How should QUSRSYS normally be used?  Someone has placed
>>>output queues in this one which I would normally place into QGPL.
>>>Any opinions on this?
>Let IBM put what it wants into QUSRSYS, and keep your stuff out of it.  If
>IBM puts queues into it, that's OK.  But keep your own stuff out.  The
>normal release to release install process handles QUSRSYS properly.
>>I believe that QGPL gets cleared whenever you update the OS, so it may not
>>be a great place to put user stuff. Is this right?
>This is not correct.  QGPL never gets cleared.  Some IBM stuff is updated
>for new releases, but it never gets cleared.

Now justa justa justa justa minute...

Used to be, QGPL was where you stuffed queues (message, out, and job) and
other similar things.  Then QUSRSYS came along, and we were supposed to
stuff queues and other similar things -there-, instead of in QGPL.

Only reason I can think of is too many people 'filled up' qgpl, so they
needed a 'cleaner' library.

If not QUSRSYS and not QGPL, where?

Yes, I agree that you should NOT stuff lots of user stuff in these libs.
If you have a bunch of stuff to keep track of, create another library.
That's why we have 500-600 libraries.  *sigh*   They -all- seem to be

--Paul E Musselman

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

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