RE: Command defaults (was: Interested in creating a 'Gotcha' list)

> You might find this interesting ... Changing OS/400 Command Defaults.
> Seems to me there is a gotcha here with respect to how to 
> handle OS/400 upgrades when you doing this kind of thing.
> http://www.itjungle.com/fhg/fhg101905-story03.html

The article is how to handle command defaults.  I have read that way to do
it (CRTDUPOBJ, etc) for years now and don't like it.  Here's how I do it.

I have a CL program, DFLTCMD, where I put all changes.  It looks like this:

/* CHANGE COMMAND DEFAULTS */
   PGM
 
/* COMPILES ARE TO BE INDENTED */
   CHGCMDDFT  CMD(CRTBNDRPG) NEWDFT('INDENT(1)')

/* COMPILES ARE TO USE DATE/TIME CONVERSION */
   CHGCMDDFT  CMD(CRTRPGPGM) NEWDFT('CVTOPT(*DATETIME)')
   CHGCMDDFT  CMD(CRTRPTPGM) NEWDFT('CVTOPT(*DATETIME)')
 
/* SQL RPG COMPILES ARE TO BE NO COMMITMENT CONTROL */
   CHGCMDDFT  CMD(CRTSQLRPG) NEWDFT('COMMIT(*NONE)')
   CHGCMDDFT  CMD(CRTSQLRPGI) NEWDFT('COMMIT(*NONE)')
 
/* SQL RPG CURSORS TO CLOSE WHEN PROGRAM ENDS */
   CHGCMDDFT  CMD(CRTSQLRPG) NEWDFT('CLOSQLCSR(*ENDPGM)')
   CHGCMDDFT  CMD(CRTSQLRPGI) NEWDFT('CLOSQLCSR(*ENDMOD)')
 
/* SET LOG TO NOLIST */
   CHGCMDDFT  CMD(SIGNOFF) NEWDFT('LOG(*NOLIST)')
 
/* Needed to retrieve the correct "WORK STATION I-D" in batch. */
   CHGCMDDFT  CMD(SBMJOB) NEWDFT('MSGQ(*WRKSTN)')
 
/* START PRINTER WRITER TO ALIGN BASED ON FILE */
   CHGCMDDFT  CMD(STRPRTWTR) NEWDFT('ALIGN(*FILE)')
 
   ENDPGM

I have a job schedule entry that runs every night that calls this program.
That way it's always up to snuff.  In addition, by having this CL, I have
documentation on every command default I changed.

I have another CL program, DFLTPRTF, that changes defaults on system print
files.  It gets called in that same job schedule entry.

YMMV but it works for me.