RE: Command Defaults and Query

[Dwayne Lindner <Dwayne.Lindner@xxxxxxxxxxxxxxxxxxxxxx>]

Thanks for the tips Alister.  We actually found an old CL written back in 97
to do exactly that - it was last run when the company upgraded to V4R3 -
unfortunately I've only been here two months so I'm not fully aware of the
ways things are done as yet.  However, as always, danger lurks.  We have two
other As/400's that are being upgraded here in the next few weeks, and we
don't believe the CL solution has been implemented - is there any way to
discover the changes that have already been made so we can create a CL to
change the new system when it's upgraded ?

Thanks!!

Dwayne Lindner
Senior Analyst - Data Centre
Wesfarmers Rural Division
184 Railway Parade, Bassendean WA 6054
Ph: (08) 9273 5365
Email: dwayne.lindner@writ.wesfarmers.com.au


-----Original Message-----
From: MacWheel99@aol.com [mailto:MacWheel99@aol.com]
Sent: Wednesday, 20 December 2000 5:50 AM
To: MIDRANGE-L@midrange.com
Subject: Re: Command Defaults and Query


> From: Dwayne.Lindner@writ.wesfarmers.com.au (Dwayne Lindner)
>  
>  Just wondering if there is any way to recover (or even save) the changed
>  command defaults (from CHGCMDDFT) after doing an upgrade - we went V4R3
to
>  V4R5 over the weekend and are now having all sorts of problems.
>  
>  The other problem we have is that queries appear to be taking a lot
longer
>  than usual....  still gathering info about that though.

In theory it is very easy to change OS/400 stuff on the fly as needed, but
in 
reality this is only effective until the next OS/400 upgrade, so your method

of making changes needs to factor in the fact that you will probably have 
some upgrade in your future.

There are several ways to plan for that, such as incorporating your changes 
into a CL.

You have one more change ... add it to the CL & rerun the whole lot.
Along comes OS/400 upgrade, when finished run the CL & be back to normal, 
although you may wish to review what if anything OS/400 did to the commands 
you are changing.

Another approach is to have copies of the changed commands in library list
in 
front of QSYS version with your changes there, leaving the QSYS stuff
vanilla.

But now that you have done your upgrade, getting at the old story would need

getting at the changed story in backup of old OS/400 & if you have not kept 
good records of what you changed, you got your work cut out for you.
+---
| 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
+---