RE: File Transfer Problems after V4R5M0 upgrade.

Julio, Joe

I can't possibly agree more...!  I'm not always real organized, but this is
one discipline I try to keep up with.  It's saved me much frustration.

Other things mentioned on this list in the past:

CHGJOBD
CHGOUTQ
CRTMSGQ (ex: QSYSMSG)
CHGMSGD (ex: CPX2313)

jt


| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of Joe Pluta
| Sent: Thursday, December 06, 2001 2:43 PM
| To: midrange-l@midrange.com
| Subject: RE: File Transfer Problems after V4R5M0 upgrade.
| Importance: High
|
|
| > From: Julio Domingo
| >
| > Darren,
| > That does sound like an authority problem.  When you install a
| new release
| > user authorities, printer file defaults, and system values are
| set back to
| > the IBM defaults.  I have found it a good idea to set up a CL
| program that
| > restores changes made between releases.  This way you can run
| the program
| > after the release install and run into less GOT YOUs.
| >     Julio
|
| This is a good idea for any number of things.  Some other examples:
|
| 1. System reply list entries
| 2. Pool sizes
| 3. Subsystem descriptions
| 4. Command defaults
|
| And even if you have a special "system" library above QSYS (many people do
| this to override certain commands or object attributes), you should have a
| program that populates this library.  This is especially true if
| the objects
| there were originally created using CRTDUPOBJ from system objects.
|
| Joe Pluta
| www.plutabrothers.com
|