I do pretty much the same thing as Jerry. Our own USRSYS library at the
top of QSYSLIBL and a CL named NEW_OS that gets run to do a number of
things like authority changes and duped commands with changed defaults.
Same thing for a couple of vendor products that we change some defaults
on.


david@xxxxxxxxxxxx 10/15/2008 6:46:38 AM >>>
Jerry Adams wrote:
First, I created a library which precedes QSYS in the system portion
of the library list.

Second, beginning in, I think, V5R4 (maybe R3) you have to be aware
of what are known as proxy commands. CRTBNDRPG is such a command.

Third, I wrote a CL that makes copies of the commands I want to
modify into the library mentioned in step #1. It, also, serves to
document the commands and the changes to the default values.

You need to be careful with this, however, as command parameters change
from release to release ... so, if you put this library higher than qsys
on the system library list, you replicate the commands immediately after
the release upgrade so applications don't start failing because they are
running the old releases commands instead of the new releases commands.

david


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