Sometimes applying or accepting PTF's does not include all the PTF's that were selected to be applied or accepted. Why are some of these PTF's being excluded?
Release : 6.0
Component : CA Datacom/AD
Some PTF's are excluded because they are being superseded by other PTF's that were selected to be applied or accepted. Some PTF's are PE'ed/marked in error an the PTF's that fix these PE'ed PTF were not selected to be applied or accepted.
Note on the left were it says ERROR where it shows two PTF's are in error. RO45502 and SO12876. On the right side of the panel RO60266 fixes RO45502 and LU02099 fixes SO12876. If RO45502 and LU02099 were not selected then RO45502 and SO12876 will not be applied or accepted. On the summary panel you can see these two PTF's in error were excluded.
To verify whether these PTF's are in error and might have fixing PTF's, in CSM go to Settings, System Settings, Software Catalog and note the path that is in the Root Directory field. For example /parentpath/mpm/scroot.
Go into ishell and access path /parentpath/mpm/scroot/DatabaseM/CA/error_hold_data
select file ALL-HOLDDATA.TXT and search for PTF's RO45502 and SO12876, You would find these:
++HOLD(RO47505) ERROR FMID(CABDE00)
REASON(AR47505) DATE(15121) CLASS(PE)
PROBLEM DB-5053: NATIVE EXTRACT/BACKUP W/FIRSTKEY FAILS
OR EXTRACT 0 RECORDS
++HOLD(SO12876) ERROR FMID(CAW1F00)
REASON(AS12877) DATE(21193) CLASS(SECINT)
PROBLEM CAIRIM-14195: SECURITY OR INTEGRITY PROBLEM
This tells us that for RO45502 and SO12876 to be included in an apply or an accept RO80879 and LU02099 must also be included. If you do not see FIX(...) identifying a fixing PTF it means one is not yet available.