II12867: ADDITIONAL SMP/E HOLDSYSTEM REASON IDS

APAR status

• Closed as canceled.

Error description

• New HOLD SYSTEM Reason IDs
  
    In addition to the existing HOLD SYSTEM reason IDs (ACTION,
    AO, DELETE, DEP, DOC, EC, EXRF, IOGEN, and MSGSKEL) several
    new HOLD SYSTEM reason IDs are being added (DB2BIND, ENH,
    EXIT, IPL, RESTART, DDDEF, DOWNLD AND MULTSYS).  These new
    reason IDs will be used where only ACTION HOLDs were used
    previously.  These new REASON IDs will allow system
    programmers more granularity in the ability to bypass SYSTEM
    HOLDs when they know they will perform the documented action,
    or when they know the action does not apply to their
    environment.  For instance, if a customer knows they plan to
    perform an IPL with a CLPA after service is installed, a
    BYPASS HOLDSYS(IPL) could be coded during the install.
    There would be no need to read HOLDDATA for SYSTEM HOLDs
    with a reason ID of IPL.
  
    Conversely, customers may choose to wait and install service
    containing a particular HOLD reason until they are ready to
    take the specified action or make the indicated change on
    their system.  With the new HOLD reason of ENH
    (enhancement), the installation of new function could be
    done at a time other than the installation of regular
    preventive service.  By not coding a BYPASS HOLDSYS(ENH),
    any new function PTFs would not be installed.
  
    There are no SMP/E changes required to recognize these new
    reason ids.  Any release of SMP/E will work.
  
    Implementation of these new reason IDs by IBM will roll out
    as internal processes are updated.  There is no defined
    order for the products or elements to implement these new
    reason ids.
  
    The new HOLD SYSTEM reason IDs and their definitions are
    listed below.  For a complete list of HOLD reason IDs (and
    their descriptions), see z/OS SMP/E Reference.
  
    DB2BIND
      A DB2 application REBIND is required to activate the
      change incorporated in the PTF.
  
    ENH
      The PTF contains an enhancement to the existing product.
      This is normally used with new function PTFs.
  
    EXIT
      Change to sample user exit or interface.
  
    IPL
      The PTF requires a system IPL with special requirements
      (e.g., IPL with CLPA) after the application of the PTF for
      the PTF to become effective.
  
    RESTART
      This PTF requires special instructions regarding subsystem
      restart.  This does not include service that requires
      normal subsystem restart to be effective.
  
    DDDEF
      Dataset changes or additions are required
  
    DOWNLD
      Code that is shipped with with maintenance needs to be
      downloaded.
  
    MULTSYS
      This Keyword identifies fixes that need to be applied to
      multiple Systems, in one of three cases; preconditioning,
      coexistence, or exploitation.
  
  Changes to SMP/E APPLY Commands
  
    You may need to change the parameters on the SMP/E APPLY
    command in order to process PTFs with these new REASONIDs.
    For example, if you currently install preventive service and
    qualify the types of SYSTEM HOLDs to be bypassed, you will
    need to add the new REASONIDs (after their HOLD condition
    has been satisfied or evaluated as not relevant to your
    environment).  If you don't have any user exits and always
    IPL with a CLPA after installing service, a sample APPLY
    command would look like:
  
      APPLY CHECK XZREQ
      GROUPEXTEND(NOAPARS,NOUSERMODS)
      SOURCEID(HIPER,PRP,YR2000,RSU98*,RSU99*,RSU00*)
      BYPASS(HOLDSYSTEM(DOC,EXIT,IPL),HOLDUSER) .
  
    Notice that EXIT and IPL were added to the types of system
    HOLDs being bypassed.  This instructs SMP/E that it is OK to
    install PTFs which require changes to user exits or require
    special IPL instructions.  This would not install any PTFs
    that required DB2 application rebinds, special instructions
    for restarting subsystems nor any PTFs that contained
    functional enhancements.
  
    Letting SMP/E filter out PTFs that were held for DB2BIND,
    ENH and RESTART will result in a return code of 08 (as is
    the case whenever a HOLD condition is not satisfied).  If a
    return code of 04 is of extreme importance, you can review
    the APPLY CHECK output and add any PTFs whose HOLD condition
    is not met to an EXCLUDE parameter to the above APPLY
    command.  This will remove the PTFs from SMP/E selection
    consideration.
  
  HOLDDATA Summary Reports
  
    In order to help customers process their HOLDDATA more
    easily, z/OS Release 1.2 SMP/E will provide HOLDDATA Summary
    reports.  These reports will provide the system programmer
    with ++HOLD information in the context of his/her SMP/E
    APPLY or ACCEPT processing output.  Having the ++HOLD
    information available with the other APPLY or ACCEPT output
    will free the system programmer from having to collect this
    information before analyzing the APPLY or ACCEPT processing
    results.  This should save significant time for the system
    programmer.
  
    There are three new HOLDDATA Reports. They are:
  
    Unresolved Hold Reason Report
      This report is a report of SYSMODs terminated because of a
      HOLD condition.  This report is sorted by ++HOLD type and
      includes the ++HOLD statements.
  
    Bypassed Hold Reason Report
      This report is a report of SYSMODs that had a HOLD
      condition bypassed.  This report is sorted by ++HOLD type
      and includes the ++HOLD statements.
  
    Summary of Bypassed and Unresolved HOLD Reason Report
      This report is a report of HOLD reason IDs that caused
      termination or were bypassed and the SYSMODs affected for
      each.  This is a summary report and does not include the
      actual ++HOLD statements.  It is also sorted by ++HOLD
      type.  Users can have certain HOLD reason types suppressed
      in their reports by using an SMP/E options entry.
  
  The SHARE presentation from which this summary is drawn is at
  url http://ps.software.ibm.com/www/usa/images/holddata_maintenan
  ce.pdf
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• APAR for information only
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels