Re: Apparently Hosed V5R3 Install - Resolution

One of our steps in our i5/OS upgrade process is to list the libraries in
the system library list, and then we remove any libraries above QSYS in the
system library list just prior to an i5/OS upgrade. Then we look at all the
objects in that library to determine if they need a "refresh" from something
they modified. We recommend that customers have a CLP called osupgrade, and
any changes they make to commands and defaults are put into that CLP, and
then we can just run that after an upgrade. Not everyone is good at putting
stuff into this CLP as they make changes, but we do have quite a few that
do.

When we go into a new account, we wind up spending sometime analyzing the
objects in the library above QSYS, as it will have to go back into the
system library list after the upgrade, and we don't want compatibility
issues once it is back in the library list.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Friday, February 20, 2009 7:51 AM
To: Midrange Systems Technical Discussion
Subject: RE: Apparently Hosed V5R3 Install - Resolution

Bill,

Thanks for the follow-up. I, too, have a system library list with a user
library above QSYS, which contains modified (defaults) for some commands.
Never had a (known) issue before, but it seems prudent to add a step to my
project plan that specifies changing the list order before applying PTF's.

Thanks.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bill
Sent: Thursday, February 19, 2009 7:58 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Apparently Hosed V5R3 Install - Resolution

After spending over an hour with Software Support, we finally pinpointed
the culprit: there was a user library ahead of QSYS which contained a
number of commands. In this case, the important command was CrtUsrPrf.
One of the PTF's, and a verrry early one at that, specified a
parameter that did not exist at V5R1, thus the PTF blew up since the
process returned an error in the process. Once the library was moved to
the bottom of the System Library List, I was able to subsequently apply
the PTF(s).

Thanks to everyone for their suggestions.

Bill