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
-- 
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From:
Simon Coulter <shc-Q/[email protected]>
To:
Security Administration on the AS400 / iSeries <security400-Zwy7GipZuJhWk0Htik3J/[email protected]>
Date:
04/15/2009 04:12 PM
Subject:
Re: [Security400] SF99608:  610 Group Security, PTF Group Level:  6
Sent by:
security400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]




On 16/04/2009, at 4:15 AM, Mayer, Michael (CMA Consulting) wrote:

> On 1 box, a PTF in a group shows as superseded and on the other box 
> that same PTF in the same group shows as permanently applied.
> PTF's were installed about 2 weeks apart using the same instruction 
> set from IBM.
> Does anyone know how this could occur?

The second machine had the permanently applied PTF installed before 
applying the group PTF. The first machine did not.

Permanently applied means the PTF was loaded and applied (either 
temporarily or permanently) and then a later PTF was installed.

Superseded means the PTF was never installed (or was but was removed) 
and a later PTF was applied. THe supersede chain that is part of the 
later PTF causes this effect.

Regards,
Simon Coulter.
--------------------------------------------------------------------
    FlyByNight Software         OS/400, i5/OS Technical Specialists

    http://www.flybynight.com.au/
    Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
    Fax:   +61 2 6657 8251                                   \ /
                                                              X
                  ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400) 
mailing list
To post a message email: Security400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.



_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400) mailing list
To post a message email: Security400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.