RE: Command defaults changed after upgrade --> V4R4

John,

A little more technical detail: IBM replaces all of the command objects in QSYS
at every release upgrade, consequently default changes made to them will
disappear, as you saw.  Many people (including me) think it's a good idea to
only make changes to a copy of the command put in a "higher than QSYS" library.
You might think that that gets you out of the woods when you upgrade, but you
would be mistaken.  In order to be sure that everything works correctly and
efficiently, you need to delete the copies and create new ones after each
upgrade.  If you don't, you could have problems with help not matching,
performance issues due to the command copies "losing" the SEPT offset to get to
their processing programs, and outright failures due to parameter mismatches.

Basically, what it comes down to is that if you customize IBM commands in any
way, you need to re-apply your customizations every time you upgrade releases.

Dave Shaw
Spartan International, Inc.
Spartanburg, SC

-----Original Message-----
From: JFinney@omnia.co.za [mailto:JFinney@omnia.co.za]

Hi All,

Just something I found particularly interesting.

 We upgraded our systems (2 AS/400's) from V4R3 to V4R4 over the weekend. I
was surprised to find out this morning that the command defaults that had
been changed using the CHGCMDDFT CL command had been reverted back to their
"former glorious defaults".

We never copied these commands, (which perhaps we should have), prior to
changing them as it was only a few (eg. the parm UPDPROD on the STRDBG cmd
was changed from *NO to *YES).

Just out of curiosity, is this a default action of the upgrade process and,
if so, can it be changed to allow for those cmds which have had changed
defaults ?
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---