RE: Apparently Hosed V5R3 Install - Resolution

Good point, Rob. The program that I run after OS upgrades takes this into consideration by re-creating the command in MODLIB and, then, applying the changes. Seems like, bearing your points and Bill's problem, that it would be prudent to (a) remove MODLIB from SysLibl, and (b) running the program to re-create the changes from scratch for both OS upgrade and PTF installs. Whether necessary in every case or not, it only takes a minute to do this so it's going onto my project plans.

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 rob@xxxxxxxxx
Sent: Friday, February 20, 2009 8:43 AM
To: Midrange Systems Technical Discussion
Subject: RE: Apparently Hosed V5R3 Install - Resolution

If a ptf tries to fix a command, then perhaps something was broken?
Meaning, Jerry, if you simply take MODLIB out of the system library list
when applying a ptf and put it back in after the ptf is applied then the
copy in QSYS will be fixed but not your copy in MODLIB. And you could
start having the issue. For example, let's say the CPP for CRTUSRPRF was
IBMPGM1 before the ptf and IBMPGMB after the ptf. And IBM deleted
IBMPGM1. Then your command would try to call IBMPGM1 and abort.

Rob Berendt