RE: compile problem

Rob and others,

Everyone says to not change the command defaults in QSYS but to do the
CRTDUPOBJ into another library higher in QSYSLIBL. I don't. I change the
defaults in QSYS.

I have the following CL program:

/* 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

It is run every night via the job scheduler, so I don't have to think about
it. I have similar programs to:

1) change all IBM supplied print files to our format (cpi, lpi, etc)
2) change all TAA tools print files to our format
3) change all Abstract print files to our format
4) change all ProGen Plus files to our format
5) miscellaneous other authorities and whatnot

Each of these is run every night via the job scheduler. I have been doing
it this way at least 15 years without a problem.