Format and explanation of data

Figure 1. Missing FIXCAT SYSMOD report, part 1

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

MISSING FIXCAT SYSMOD REPORT FOR ZONE nnnnnnn

                                 HOLD            MISSING       HELD         ______RESOLVING SYSMOD______
FIX CATEGORY      FMID           CLASS           APAR          SYSMOD       NAME       STATUS   RECEIVED
------------      ----           -----           -------       -------      ----       ------   --------
aaaaaaaaaaaa
                  bbbbbbb        ccc             ddddddd       eeeeeee      fffffff    gggggg   hhhhhhhh
                  bbbbbbb        ccc             ddddddd       eeeeeee      fffffff    gggggg   hhhhhhhh

These are the fields in the first part of the report:

FIX CATEGORY

is the fix category specified on the CATEGORY operand of the ++HOLD MCS. If multiple fix category values are specified for a particular ++HOLD, that HOLD is reported once for each fix category value that matches any of the fix categories of interest specified by the user. If no missing SYSMODs exist in the zone, this field will contain ***NONE.

FMID

is the FMID of the held SYSMOD.

HOLD CLASS

is the hold class specified on the CLASS operand of the ++HOLD MCS. If the CLASS operand is not specified on the ++HOLD, this field is blank.

MISSING APAR

is the unresolved HOLD reason ID.

HELD SYSMOD

is the ID of a SYSMOD that has an unresolved HOLD condition.

RESOLVING SYSMOD NAME

is the list of SYSMODs that can resolve the HOLD reason ID. If a fixing SYSMOD is identified in the RESOLVER operand on the ++HOLD MCS, then that SYSMOD is included in this list. If other SYSMODs exist in the global zone that supersede the reason ID APAR, then they are also be included in this list. If no SYSMODs are in the list, then this report field will contain the value ***NONE.

RESOLVING SYSMOD STATUS

describes the current state of the SYSMOD that resolves the HOLD.

GOOD: The SYSMOD is not held and has no known problems.
HELD: The SYSMOD is held because one or more error HOLDs exist for it.

RESOLVING SYSMOD RECEIVED

indicates whether the resolving SYSMOD has been received and is found in the global zone or not.

Resolving SYSMODs identified in the missing FIXCAT SYSMOD report might have a status of HELD. This means one or more error HOLDs exists for them. To identify SYSMODs that resolve these error HOLDs, the second part of the missing FIXCAT SYSMOD report is produced. In addition, any of the resolving SYSMODs that are held for an error are also included in the second part of the report. If none of the resolving SYSMODs identified in the first part of the report are held for an error, then this second part of the report is not produced.

Figure 2. Missing FIXCAT SYSMOD report, part 2

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

MISSING FIXCAT SYSMOD REPORT FOR ZONE nnnnnnn								- FIXES FOR HELD RESOLVING SYSMODS

HOLD          HELD                          ______RESOLVING SYSMOD______     HOLD
FMID          SYSMOD      APAR              NAME      STATUS    RECEIVED     CLASS
----          ------      ----              ----      ------    --------     -----
aaaaaaa       bbbbbbb     ccccccc           ddddddd   eeeeeee   gggggggg     hhhhhhh
                                            ddddddd   eeeeeee   gggggggg     hhhhhhh

These are the fields in the second part of the report:

HOLD FMID