Interatcive Debug

[Guest.Visitor]

You can use the command: CHGCMD CMD(QSYS/STRISDB) PMTOVRPGM(Your_Lib/Your_Pgm) to override the prompt override program.

[trevor.lazarus@ssa.gov]

CHGCMDDFT CMD(STRISDBG) NEWDFT('updprod=*YES')

[Guest.Visitor]

This command is very helpful if you will change your default permanently like I did in my CRTDSPF file, I change RSTDSP = *YES. Sky

[Guest.Visitor]

While the above means of changing the commands' defaults are correct. You should NEVER change the commands in QSYS directly. 1) If you mess up & haven't made a backup, you're hosed. 2) There's no quick way of telling which commands have been modified and HOW. 3) When you upgrade to another release, ALL command mods are lost. The recommended technique: 1) crtdupobj qsys/cmdname qusrsys/cmdname objtype(*cmd) 2) Modify the command in QUSRSYS; i.e., CHGCMDDFT CMD(qusrsys/STRISDBG) NEWDFT('updprod=*YES') 3) Insure your System library list has QUSRSYS above QSYS. Then, by just looking at commands in QUSRSYS, you can tell which were modified. By comparing them with the ones in QSYS, you can tell WHAT was modified. If you did mess up, just dltcmd qusrsys/cmdname & start over. When you upgrade, you compare your QUSRSYS commands with the new ones in QSYS to insure no changes were made to the commands which would cause problems with YOUR version in QUSRSYS.

[Guest.Visitor]

It seems to me that I read an article a while ago that said that after V5R1M0, IBM would be changing some commands so that they would always run out of their supplied library no matter what other versions might be on the system. The article also specifically mentioned not doing what you suggest, and what most of us used to do, because of this change. Alan

[T.Holt]

Here's an article on the web that addresses that & other V5R1 gotcha's. Look for "Command Processing Changes" on the 2nd page. V5R1 Gotcha's (http://www.help400.de/Download/V5R1Gotchas.doc)

[gary.shipp@s3t.co.uk]

Is QUSRSYS the recommended place to put the amended commands, or is it better to create a new library?

[Shannon_Wolf]

Could anyone tell me how I can change default of "update production files" to *YES? When typing the STRISDB command and prompting, I would like to had this field to default to *YES. Any and all help is greatly appreciated. Shannon Wolf <hr width=50 align=left>Code ('http://www.mcpressonline.com/mc/showcode@@.6ae5308e')

[Jeff Crosby]

William McLain wrote: > While the above means of changing the commands' defaults > are correct. You should NEVER change the commands in QSYS directly. With all due respect, I have done the above for at least 12 years with no ill effects. I store the changes in a CL program, DFLTCMDP, that looks like this: /* CHANGE COMMAND DEFAULTS AFTER A RELEASE UPDATE */ 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)') /* SET SIGNOFF 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 actually run this program every night via a job schedule entry. Therefore, if any PTF's were applied that may have replaced the command object, it gets reset the way I want it. I have a similar program, DFLTPRTF, that changes IBM supplied print file to the settings I want. -Jeff