Re: Fully automated PTF installation

For one client I recently wrote a CL program that did a
SNDPTFORD...
INSPTF...
Lather, rinse, repeat for each group.
I could have made it better by specifying
PTFID((*CUMPKG)) instead of SF99610,
*HIPERGRP instead of...
and so on...
and I should have. This makes the transition from 6.1 to what's next
easier.

Keeping in mind that the hiper group comes out almost every week. So,
unlike the one poster, no, once a quarter is not sufficient. Especially
if your like the customer I did which can afford the downtime to IPL
weekly.

And since this is for one machine, and I just order the delta, then no
need to use image catalogs, eh? Especially since I do it once a week.

Now, this ignores special instructions, like the warning to all those
running 5798FAX on the current cume. I bet they compiled that ptf to be
cross 5.4 and 6.1 and that's why they have you check the force conversion
option. They really need to upgrade 5733FXD and 5798FAX. Frankly,
5798FAX should be thrown in the OS, imnsho. This is like IBM charging
extra for the ability to print something, oh wait, they do. See "5761SS1
36 5112 PSF for i5/OS 1-55 IPM Printer Support"

Are you asking for something that does something like use a SOA access to
Fix Central, find the current list of cumes and groups for your version of
i, download them and apply them? Submit the DCR. Although some people go
nuts when they see the groups for versions of WAS they don't have loaded.
PTF Group Level Status
SF99351 2 Not applicable
SF99350 3 Not applicable


Rob Berendt