You should consider that there are two scenarios. A) PTFs during a
release upgrade and B) PTFs between releases. During A) the book clearly
states that the CUMe should be done first followed by the groups (if
any). However, I always do the HIPER group followed by an IPL. Then do
the remaining groups in no particular order and finally the CUMe with a
second IPL. Never failed me. I use the same sequence for scenario B)
except no IPL between the HIPER group and the rest but there isn't
really and IBM recommendation on those.

I have run into problems doing the CUMe and all the groups in a single
IPL during a release upgrade. Possibly just too many PTFs to handle? Not
sure but since I've started doing the IPL after the HIPERs (V4R5 time
frame) no more problems.

My logic for the sequence is this. Suppose there are three PTFs: 1, 2,
and 3.

1 is a PTF for some SLIC component and is on the CUMe
2 supersedes 1 and is required by some DB PTF and is on the DB Group.
3 supersedes 2 (and 1) and is on the HIPER group.

Clearly loading CUMe, DB, HIPER in that order will do three LODPTF and
three APYPTF (albeit temp type) commands.

If HIPER is done first then PTF 1 and 2 will already be marked as
superseded so that both the DB and CUMe loads will skip them. Saves me
time and IMHO lessens the chance for a problem with objects being
replaced over and over during the PTF load.

My .02

   - Larry

   (OS/400 upgrade veteran with the scars to prove it!)

Julio Domingo wrote:

>       I too have always applied the cume package first.  I have found that 
>some
> of the individual PTF have been included in the cume or something in the
> cume is a prerequisite.
>




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.