Applying maintenance containing HOLD statements

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC
• PanApt
• PanAudit

Issue/Introduction

How to apply ACF2 maintenance containing ++HOLD statements?

Environment

Release:
Component: ACF2MS

Resolution

Some ACF2 maintenance is packaged with ++HOLD statements. SMP/E will not apply this maintenance (PTFS) unless it is specified a BYPASS(HOLD....) statement.

Before installing any ACF2 maintenance containing a ++HOLD statement, make sure that the reasons specified for the hold are carried out.

The exact syntax needed to apply the maintenance (PTF) depends on the "type" and "reason" stated within the ++HOLD statement. For ACF2, most ++HOLD statements are for a type of SYSTEM and a REASON code of ACTION and an occasional reason of OPTIONL.

To APPLY the maintenance marked with ++HOLD, specify:

The general syntax for the BYPASS operand is:

    BYPASS(HOLDtype(reason(sysmod1,sysmod2,...))) 

EXAMPLES:

For the ++HOLD statement:

    ++HOLD(ptfName) FMID(fmidName) SYSTEM REASON(ACTION) 
       COMMENT(SEE DESCRIPTION IN APAR FOR DETAILS).      

To apply this single fix, specify:

    APPLY SELECT(ptfName) BYPASS(HOLDSYSTEM(ACTION)). 

To apply all held PTFS for ACF2 MVS with a reason of ACTION, specify:

    APPLY PTFS FORFMID(fmidName) BYPASS(HOLDSYSTEM(ACTION)). 

To apply all PTFS, but only one specific held fix, specify:

    APPLY PTFS FORFMID(fmidName) BYPASS(HOLDSYS(ACTION(ptfName))). 

When performing an APPLY CHECK, it is acceptable to specify a more generic form to include all reason codes:

    APPLY CHECK PTFS FORFMID(...) 
       BYPASS(HOLDSYSTEM). 

For the ++HOLD statement:

    ++HOLD(ptfName) FMID(fmidName) SYSTEM REASON(OPTIONL) 
       COMMENT(SEE APAR FOR DETAILS). 

To apply this optional fix, specify:

    APPLY SELECT(ptfName) BYPASS(HOLDSYSTEM(OPTIONL)).