Changing Command Defaults (was: Problem with SBMJOB andLibrary List)

["Tom Jedrzejewicz @ San Pedro" <TJedrzejewicz@xxxxxxxxxxxx>]

No the CL programs will not have to be recompiled.

As this example shows, changed command defaults, subsystem descriptions
and other "system" objects are a big gotcha when upgrading and even when
debugging.  I learned a method a while back to make this manageable.

Create a library (say QSYSCUSTOM), and put it AHEAD of QSYS in the
system library list.  Then, when the need arises to change something in
QSYS (or even QGPL), duplicate it into QSYSCUSTOM, change it there, and
note the change in the object description.  If you are really
disciplined, create a QTXTSRC in that library and describe the changes
in a member in that file.  Then, when you upgrade, re-create QSYSCUSTOM
based on the notes.

Does anyone else have a better way to deal with this?

>>> r_perno@xxxxxxxxxx 03/19/03 07:41AM >>>
<< snip>> 
 Seeing as all our code on the new box uses jobd's in the SBMJOB
commands - i am going to change the default value of parm INLLIBL to
*JOBD
with the CHGCMDDFT command.  Can someone tell me if i need to recompile
all
the CL pgms or will they work just by changing the parm.

THIS MESSAGE IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH 
IT IS ADDRESSED AND MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL 
AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW.  If the reader of this message 
is not the intended recipient, or the employee or agent responsible for 
delivering the message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, downloading, storing or forwarding of 
this communication is prohibited.  If you have received this communication in 
error, please notify us immediately via email and delete the message from your 
computer files and/or data base.  Thank you.