At 10:30 PM 12/8/97 -0500, you wrote:
>John and Al, thanks for your responses.
>>BTW, if anyone questions you as to why you're risking this change, ask them
>>how they test new program changes?  <bg>
>This is the reason why I want to move them.  Testing is a real pain.  So, to
>summarize, I need to do the following:
>    1) analyze any CHG library statements to determine what they do, and
>    2) move application specific libraries to the QUSRLIBL system value.
>    3) modify the CHG library statements appropriately, probably
>        ADDLIBLE/RVMLIBLE commands.
>Am I missing anything else?  In the future, I'd like to create group
>profiles which
>match job function.  Then create an initial library list attached to each
>profile so that each job function only uses the libraries it needs.  This
>will also
>minimize the searching for objects.

You're right.  Testing is a real pain.  That's why many people I know don't
do it. (ha ha ha).  You're approach is solid, assuming you do not submit
jobs in the S/38 environment where the INLLIBL parameter default is *JOBD
(or assuming you do not use this natively).

>By the way, I'm curious, why is there a QSYS2?  Why aren't those objects
>in QSYS?

I'm curious too.  Apparently, there's somebody in Rochester whose
compensation plan is based on the number of system libraries they can
generate.  Hopefully that person will get pinkslipped today  (you know,
today is the day!), or else the swat team unable to take out Sadam could
use said person for practice.


Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406

Private mail should be sent to
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "".
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

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