Re: CHGCMDDFT behavior confirmation

Yes, CHGCMDDFT makes a change to the actual command object.

V5R4 put a new wrinkle on things. Prior to V5R4 when you installed a LPP
it often duplicated the LPP's commands into a library often in the system
library list - like STRPDM got copied from QPDA into the various QSYS*
libraries (depending if you support multiple languages and allowed
compiling to previous releases). Starting with V5R4 the command is not
copied. Instead "proxy" commands are created that point to the LPP
library. So if you do a
CHGCMDDFT QSYS/STRPDM ...
it will also change the defaults in the command QPDA/STRPDM.
WRKOBJ *ALL/STRPDM *CMD
Object Type Library Attribute Text
STRPDM *CMD QPDA Start PDM
STRPDM *CMD QSYS PRX Start PDM
STRPDM *CMD QSYSV5R2M0 START PDM
STRPDM *CMD QSYSV5R3M0 START PDM
Notice the new "PRX" attribute? See also the new CRTPRXCMD command. We
used to duplicate vendor commands to QSYS or QUSRSYS. Now we use
CRTPRXCMD. This way if the vendor puts on new versions (and perhaps add
an option to their command or something) we always get the latest and
greatest without having to redo it all the time.

See also (for those of you who've migrated from the S/36):
CRTPRXCMD CMD(QUSRSYS/OFF) TGTCMD(SIGNOFF)

Those of you deeply familiar with the IFS can think of these as symbolic
links.

If you look in Infocenter the defaults for most IBM commands are
displayed. For example the defaults for STRTCP are *YES on all the
choices.
http://publib.boulder.ibm.com/infocenter/iseries/v5r4/topic/clfinder/name_finder.htm
(see the underlines to signify the IBM default value?)
Now, if you did a CHGCMDDFT and you're concerned whether or not the vendor
changed it back or something, then checking Infocenter may not be your
groove. Then you may wish to check object journals, object change dates,
backups, etc.


Rob Berendt