Re: Mysterious Changes since going to V5R4

[rob@xxxxxxxxx]

What I suspect happened is that you had did a 
CHGCMDDFT CMD(STRPRTWTR) NEWDFT('FORMTYPE(*ALL *NOMSG)')
in a past life and haven't yet done that in V5R4.  Now when the program in 
QSTRUPPGM system value runs it starts the writers without your default.
The archives pretty well cover suggestions to how to deal with this.  They 
include:
- Copying IBM commands into a different library.  Doing the CHGCMDDFT on 
these commands.  Putting this library higher in the library list than 
QSYS.  See system value QSYSLIBL.
- Putting a series of CHGCMDDFT's into QSTRUPPGM.  So that every IPL will 
change these for you.
Read the V5R4 MTU for CHGCMDDFT.  They are using something called "proxy" 
commands now.  Basically a proxy command may be likened to an IFS symbolic 
link.  Or if you're Windows aware it's like a link instead of a copy.  So 
if you change the proxy command, which only points to the command in 
another library, then it changes that command.  For example
QSYS/CRTBNDRPG is a proxy command that points to QDEVTOOLS/CRTBNDRPG.  So 
if I do a CHGCMDDFT on the one in QSYS it also changes the one in 
QDEVTOOLS.
You can see this with DSPCMD QSYS/CRTBNDRPG.
You may not give a rip.  But if associates are in the habit of qualifying 
libraries to get around you changing command defaults then they'll now 
discover that the command may be changed in that library also.
IBM often qualifies the library in a command.  Perhaps to get around the 
people who copy their commands into a library high in QSYSLIBL.  Again, 
check that out in QSTRUPPGM.

Is the data queue rebuilt on a daily basis?  Is the authority on
CRTDTAQ DTAQ(...) AUT(*LIBCRTAUT)
sufficient?  That is the default, as shipped.  (Unless I changed all my 
machines and forgot about it - which is highly possible.)  That basically 
says to use what is in the library it was created in.  Like, if you did a 
CHGLIB LIB(...) CRTAUT(*ALL)
Then all objects created with commands that have a default of 
AUT(*LIBCRTAUT) will adopt the CRTAUT of the library.  Now, IBM seems 
rather random in what value they assign to the AUT parameter for the 
various CRT* commands.

Rob Berendt