Definitely in a diffferent library as Dave suggests. Also, create a CL
that you run after a release upgrade. Just keep adding all your changes
to this. You may only run it every couple of years but it's well worth
doing. Object Authority changes, duping commands and changing the
defaults.... all that good stuff.
DTurnidge@xxxxxxxxxxxxxxxxxxxx 05/09/2007 1:08:14 PM >>>
The "string" is the appropriate parameter followed by the entry you
desire in parens, all in single quotes...
Per Bob: CHGCMDDFT CRTBNDRPG 'DBGVIEW(*SOURCE)'
This only needs to be run when your command changes, usually by
upgrading your system.
What you ... SHOULD ... do, is copy the command to a library above QSYS,
and change THAT command. Then when you upgrade the next time, YOUR
command won't change. HOWEVER, then you have the problem of IBM changing
the parms of a command, and then you blow up because of THAT reason....
SO, create your library that sits above QSYS. Ours is MUSER. Write a
program that
1) deletes the command from your library (MUSER),
2) copies the new command from QSYS to your library (MUSER). At this
time you can rename the command if you wish (for example WRKACTJOB to
WAJ).
3) Next, do the CHGCMDDFT command as you wish.
Now you have a program to run after each install, and it will bring your
"in house" IBM copies up to date...
Dave
midrange.com
