|
The -proper- way to change command defaults for IBM commands is to create a library (OURQSYS) and place it ahead of QSYS in the system portion of the library list:
OURQSYS
QSYS
QGPL
QTEMP
etc.
To change a command default, CRTDUPOBJ from QSYS to OURQSYS, then change command default on the copy in OURQSYS.
The important thing to remember is to delete and re-create your copy of the command after every OS upgrade-- the command or program may have been changed.
We keep a program for all such changes-- it deletes, re-dupes, and re-applies the changes for all the commands we've mangled.
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
.
At 4:36 PM +0100 2/22/17, D*B wrote:
<Barbara>
Also, changing the default for PPGENOPT to *NOSEQSRC probably wouldn't be a good idea because then the compiler would only operate in preprocessor mode.
</Barbara>
... changing a command default (or any other global setting) propably would never (in words: never!!!) be a good idea!!!
- it could be changed maybe back by every PTF and for sure by a new release
- every use of the command in a programm could change it's behaviour
- for CRTxxx commands, every recompile of an object could change the behaviour of the object
only (sorry) fools could recommend to change command defaults, or other global settings!
As an Amazon Associate we earn from qualifying purchases.
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.