MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2008

Re: Cume, Group



fixed

hmmmm.... well, image catalogs are terrific. But... and this is a big BUT... don't always count on the Verify of image catalogs to tell you the complete truth. You can actually verify an image catalog that is missing a component because of a bad CD (such as SS1, option 3, Extended Base Support. I know, it just happened to me on V5R3 to V5R4) that spans more than one CD. It appears that the verify only checks the header contents, not the entire feature. NOW, while this is true of Upgrades, it rarely, if ever, happens with PTFs.

I echo Dr. Franken's thoughts on this. However, with V5R4, it's pretty much load them all to a virtual and verify with sort. Then apply in one fell swoop, just use option 3 on the multiple sets parameter, except when upgrading the OS version or release. Then, don't screw with it, just do the Cume first, then the groups. Any other time, the full sort and load will suffice. It may do a "double, double" ipl, but it knows about this stuff now.

The Cume package these days, come with the hipers and the DB PTFs rolled in. The last time that I _HAD_ to load them separately without doing an upgrade, was with V5R1. I have not seen those issues since then.



Roger Harman wrote:
I do it oldest to newest for the reason you mentioned - I don't want to
have a missing pre-req. I'd rather spend the extra time installing the
cume first and then overlaying parts of it if there are superceding
PTF's in a group or hiper.

I second Jerry's endorsement of image catalogs - those are the best. Recently, I had a couple of bad CD's. Would have hated to find out
midway into the load. With image catalogs, I knew ahead of time and
could get them replaced.


lbolhuis@xxxxxxxxxx 07/18/2008 1:01:37 PM >>>
IBM Says Cume first then groups.

>From V5R3M5 and forward I ALWAYS Load them all up in one giant image catalog and let them fly. For V5R3M0 and previous you need to know how
far behind you are before you do that or you risk making the link loader go 'Tilt' and then having to reload the LIC. (No customer data is harmed
in this, but downtime ensues.) You can safely do about 1 years worth of
PTFs at a time but if you're further back than that you want to do the CUME
by itself with an IPL and then add other groups. Remember that the HIPER
and the DB groups are in the CUME.
Logically it makes sense to do the HIPER first because those are the
most current. The HIPER will lay down a big bunch of 'Superceded's which will

mean the CUME and other groups won't have to apply those PTFs only to
have the HIPER come along and overlay them. However occasionally IBM expects that a particular CUME level is already installed before the HIPER is installed. Given that, there is the "WHY" for doing the CUME first and then the HIPER and other groups.

- Larry


Larry Bolhuis IBM Certified Advanced Technical Expert
- System i Solutions
Vice President IBM Certified Systems Expert:
Arbor Solutions, Inc. System i Technical Design and Implementation V5R4
1345 Monroe NW Suite 259 eServer i5 iSeries LPAR Technical Solutions, V5R3 Grand Rapids, MI 49505 IBM Certified Specialist System i Integration with BladeCenter

and System x V1
(616) 451-2500 System i IT Simplification: Linux Technical V5R4
(616) 451-2571 - Fax iSeries System Administrator for
OS/400 V5R3
(616) 260-4746 - Cell
If you can read this, thank a teacher....and since it's in English, thank a soldier.





Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx
07/18/2008 03:27 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Cume, Group






I looked for the "why" in the archives and couldn't find it...

For once and for all I want to understand in my mind which you do first and why: cume or group? I ordered groups and cumes, and I want to know which to do first, and what's the reasoning.

Joe






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact