Re: SF99608: 610 Group Security, PTF Group Level: 6

I don't think so Simon. I can permanently apply a ptf as soon as I put it
on and not have a later ptf.

On the one that says superseded, what ptf superseds it? I bet the other
machine does not have that ptf. For example

Product ID/PTF ID . . . . . . . . . . : 5761999 MF46499
Release . . . . . . . . . . . . . . . : V6R1M0
PTF status . . . . . . . . . . . . . . : Superseded
Latest superseding PTF . . . . . . . . : MF46504
Superseded by . . . . . . . . . . . . : MF46504

Product ID/PTF ID . . . . . . . . . . : 5761999 MF46523
Release . . . . . . . . . . . . . . . : V6R1M0
PTF status . . . . . . . . . . . . . . : Permanently applied
Latest superseding PTF . . . . . . . . : None


If I had another lpar that had MF46499 and if it was only Permanently
applied then that other lpar would not have MF46504 either perm or temp
applied. It may have it loaded and set to apply at the next ipl.

There might be numerous reasons why a ptf did not apply. More common
reasons were:
- ptf's were not ordered at the same time.
- lack of an ipl, or if there was an ipl you had an 'abnormal' ipl. You
may not have noticed it but if you do a DSPSYSVAL QABNORMSW it may show
abnormal. Just so much as doing an ENDJOBABN will make the next IPL
abnormal.
- someone ordered an individual ptf on one machine but not another
Less common may include items like damaged ptf, etc.
You can search IBM documentation for the superseding ptf to see if it was
on a group, cume, etc.


Rob Berendt