RE: Command defaults changed after upgrade --> V4R4

Yes, this one always catches people out. 

-----Original Message-----
From: JFinney@omnia.co.za [mailto:JFinney@omnia.co.za]
Sent: Monday, February 21, 2000 8:42 AM
To: MIDRANGE-L@midrange.com
Subject: Command defaults changed after upgrade --> V4R4


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 ?

Regards
John.


+---
| 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
+---
+---
| 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
+---