Re: Cume, Group

Chuck

These days if you order a cume, you also get the DB2 and the HIPER groups. They are not considered to be "in" the cume, however, they are still separate. They do not flow into the contents of the cume CDs, for instance.

Oh - here's a link that says this--

http://www-304.ibm.com/systems/support/i/fixes/guide/faqs.html#v5cum

Cheers
Vern

-------------- Original message --------------
From: CRPence <CRPbottle@xxxxxxxxx>

Larry Bolhuis wrote:

<> 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. <>

Is there some documentation suggesting that "the HIPER and DB groups
are in the" cumulative? I am almost positive that is untrue for the DB
PTFs. Since non-HIPer groups are established on a schedule outside of
the cumulative, any newer PTFs would not be on the current cumulative,
yet could still be on a group. I recall many times that the DB group
would have PTFs included that I had not yet approved for inclusion on
any cumulative; those same PTFs might not make any future cumulative.
Additionally, the next paragraph seems to contradict the statement that
the HIPer PTFs are included in the cumulative. That is, if the HIPer
PTFs are in the cumulative, then what would be the point in applying
both a HIPer group and the cumulative, when applying just the cumulative
would handle both?

Regards, Chuck
--
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.