Example

Suppose you ran the following command:

APPLY  S(UR00001) GEXT CHECK.

and the SYSMOD Status report included the results shown in Figure 1.

Figure 1. SYSMOD Status Report: Sample Report for APPLY

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


 SYSMOD STATUS REPORT FOR APPLY PROCESSING     SYSMODS APPLIED - 0

 NOTE:  '-' INDICATES THE REQUISITE SYSMOD OR HOLD CONDITION IS NOT SATISFIED
        '*' INDICATES THE NON SATISFIED REQUISITE SYSMOD OR HOLD CONDITION IS BYPASSED
        '#' INDICATES THE SUPERSEDING SYSMOD WAS NOT PROCESSED

 SYSMOD   STATUS    TYPE      FMID      REQUISITE SYSMODS, SUPBY SYSMODS, HOLD REASON-IDS, AND CAUSER SYSMODS

 AR00001  NOGO                          SUPBY  #UR00002

 UR00001  HELD      PTF       HROOTC1   HOLDE  -AR00001
                                        CAUSER  UR00002

 UR00002  HELD      PTF       HROOTC1   HOLDE  -AR00003
                                        CAUSER  UR00002

In this case, the report indicates that APPLY processing failed for SYSMODs UR00001 and UR00002 because of unresolved error holds. The causer SYSMOD for both PTFs is UR00002. Next, you look up UR00002 in the Causer SYSMOD Summary report, shown in Figure 2.

Figure 2. Causer SYSMOD summary report: sample report for APPLY

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

CAUSER SYSMOD SUMMARY REPORT FOR APPLY PROCESSING

CAUSER     FMID     MESSAGE ID  PAGE    ERROR DESCRIPTION AND POSSIBLE CAUSES

UR00002    HROOTC1  GIM35901I      2    ERROR HOLD AR00003 WAS NOT RESOLVED.

That report shows that APPLY processing failed because error hold AR00003 was not resolved for SYSMOD UR00002. By resolving this hold, you will fix the errors listed in the SYSMOD Status report.