RE: PTF application order

> From: rob@xxxxxxxxx
> 
> I would definitely apply the cume, groups and hiper GROUP.  I don't
mess
> with individual hipers.  Since the hiper group is updated weekly (or
more)
> that's good enough for me.  I used to mess with individual hipers but
that
> just got to be too much work.

Makes sense.  My only worry is the occasional horror story of the broken
PTF that scrambles the machine.

> In general we put all these on all systems every 8 weeks.  We have a
'toy'
> system that we put them on earlier in the week prior to the downtime
> weekend.  Then we put them on a Domino cluster backup iSeries.  Then
that
> weekend they go on the rest.  Never have we had a situation where,
after
> applying it on the early machines, have we not applied it on the rest.

I'm going to try to do this quarterly.  Should be fine for me.  Only
have te one machine on current.


> You can run the ADDIMGCLGE multiple times.  Once for each CD.

Here's the question: if I copy a file onto the IFS, then add it to an
image catalog, can I delete it from the IFS before applying the image?
I don't have a ton of extra space, so this would allow me to add a lot
more images to the catalog before running the thing.

And can I add, say, multiple group PTFs to one image?  Or should I just
bite the bullet and add the cume, and then add the PTF for WebSphere
(which pretty much adds everything else), then finally the Hipers.  

The icky thing about this approach is I have three versions of WAS, and
each requires its own group PTF, and each group PTF includes the DB2,
BMI, Java and HTTP group PTF.  So I end up loading all those stupid PTFs
every time.

Joe