Example 3: SYSTEM and USER section of the unresolved HOLD reason report

The example in Figure 1 shows both a SYSTEM and a USER HOLD. In this report you will note that the comment text supplies a lot of information about the HOLD.

Figure 1. Unresolved HOLD reason report: sample of the SYSTEM and USER section of the report

PAGE nnnn  - NOW SET TO TARGET ZONE nnnnnnn  DATE mm/dd/yy TIME hh:mm:ss SMP/E 36.nn SMPRPT OUTPUT

UNRESOLVED HOLD REASON REPORT FOR APPLY CHECK PROCESSING

NOTE: THE SYSMODS LISTED IN THIS REPORT ALSO APPEAR IN THE CAUSER SYSMOD SUMMARY REPORT.

TYPE      REASON ID   FMID    SYSMOD   ++HOLD DATA
------    ---------   ------- -------  ------------------------------------------------------------------------
SYSTEM    ACTION      HKDB310 UK12345  ++ HOLD(UK12345) SYS FMID(HKDB310) REASON(ACTION) DATE(07215)
                                                COMMENT
                                                (OA16310
                                                *******************************************************************
                                                FUNCTION AFFECTED: GDPS/XRC
                                                Geographically Dispersed Parallel Sysplex
                                                *******************************************************************
                                                DESCRIPTION : Modification to GRS Resource Name List (RNL)
                                                *******************************************************************
                                                TIMING : After APPLY and prior to restarting XRC
                                                *******************************************************************
                                                If your installation exploits the GDPS capability for the
                                                Controlling system to recover the FlashCopy devices while
                                                the system data movers remain active, an additional statement
                                                must be added to the GRSRNLxx parmlib member:

                                                RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSZXRC1)

														  									This statement is in addition to, and does not replace, the
														  									other statements required for the capability:

                                                RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSXRCMS)
                                                RNLDEF RNL(EXCL) TYPE(GENERIC) QNAME(SYSXRCLS)

                                                Note, this update is required even if you do not to intend to
                                                exploit the XRC scalability enhancements. ).

USER      DELAY       HKDB310	UK33778	  ++ HOLD(UK33778) USER FMID(HKDB310) REASON(DELAY) COMMENT(
														Delay installing this PTF. ).