|
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
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
Jerry Adams <Jerry@xxxxxxxxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
02/20/2009 07:55 AM
Subject:
RE: Apparently Hosed V5R3 Install - Resolution
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.