Example: Bypassed HOLD reason report

Note: AO and DOC appear as SYSTEM reason IDs in both the "Unresolved HOLD Reason Report" and the "Bypassed HOLD Reason Report". This could occur only if you bypassed the SYSTEM holds for specific SYSMODs.

Figure 1. Bypassed HOLD Reason Report: Sample Report

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

BYPASSED HOLD REASON REPORT FOR APPLY CHECK PROCESSING

TYPE    REASON ID  FMID     SYSMOD   ++HOLD DATA

------  ---------  -------  -------  ------------------------------------------------------------------------

SYSTEM  ACTION     HXY0022  UZ06853  ++HOLD (UZ06853) FMID(HXY0022) SYSTEM REASON(ACTION)
                                       COMMENT(INCREASE TARGET DATA SET SIZE OTHERWISE
                                       YOU WILL X37 DUE TO INCREASED LMOD SIZES).

        ACTION     JXY0033  UZ64781  ++HOLD (UZ64781) FMID(JXY0033) SYSTEM REASON(ACTION)
                                       COMMENT(SYSTEM MUST BE IPLED TO ACTIVATE THE CHANGE).

        AO         HXY0022  UZ06444  ++HOLD (UZ06444) FMID(HXY0022) SYSTEM REASON(AO)
                                       COMMENT(MUST MASSAGE AUTO OPS DUE TO NEW MESSAGES).

        DOC        HXY0022  UZ06444  ++HOLD (UZ06444) FMID(HXY0022) SYSTEM REASON(DOC)
                                       COMMENT(NEW MESSAGES).

        DOC        JXY0033  UZ64781  ++HOLD (UZ64781) FMID(JXY0033) SYSTEM REASON(DOC)
                                       COMMENT(PARMLIB MEMBER FORMAT CHANGE).