Re: Compiler Command Overrides [PRIVATE REPLY]

Hi, Paul:

That is almost exactly how I used to recommend doing this.

What you describe would have worked "fine" up to either V5R3 or V5R4, when IBM introduced "proxy" commands. Be afraid, be very afraid, because if you happen to do a CRTDUPOBJ of a "proxy" command to your QURQSYS library, and then change the defaults on it, you will actually be changing the defaults of the "real" command that the proxy points to. :-(

(I had posted to the list about this earlier...)

So, now, you need to first check to see if the command you want to duplicate is a "proxy" and if so,then you must "follow the chain" and issue the CRTDUPOBJ against the "real" command, to which it points, and not the "proxy." For example, issue DSPCMD CRTBNDRPG and notice what you see there.

Also, see the post from Barbara Morris that indicates that IBM can now sometimes add new parameters to commands via PTFs, e.g. as part of a "Technical Refresh" ... this also has serious implications that suggest avoiding this technique.

All the best,

Mark S.Waterbury

> On 2/22/2017 7:42 PM, PaulMmn wrote:

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!