Format and explanation of data

Figure 1. SYSMOD status report: standard format

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


 SYSMOD STATUS REPORT FOR xxxxxxxx PROCESSING     SYSMODS yyyyyyyy
- nnnn

 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
 aaaaaaa  bbbbbbb   cccccccc  ddddddd   eeeeeee  fffffff…
 aaaaaaa  bbbbbbb   cccccccc  ddddddd   eeeeeee  fffffff…
 aaaaaaa  bbbbbbb   cccccccc  ddddddd   eeeeeee  fffffff…
 aaaaaaa  bbbbbbb   cccccccc  ddddddd   eeeeeee  fffffff…
 aaaaaaa  bbbbbbb   cccccccc  ddddddd   eeeeeee  fffffff…

These are the fields in the report:

xxxxxxxx

is the SMP/E command being processed: APPLY, ACCEPT, or RESTORE.

yyyyyyyy

indicates the type of processing that was done: APPLIED, ACCEPTED, or RESTORED.

nnnn

is the number of SYSMODs with a status of APPLIED, ACCEPTED, or RESTORED; that number depends on the command that was processed.

SYSMOD

identifies the SYSMOD that was processed.

STATUS

describes what happened to the SYSMOD.

APPLIED, ACCEPTED, or RESTORED: The SYSMOD was successfully processed.
DELETED: The SYSMOD was explicitly or implicitly deleted.
ERROR: SYSMOD processing stopped after some target libraries or SMP/E libraries were updated, but before the SYSMOD was completely processed. A SYSMOD is completely processed when all its elements have been processed and all its requisites have been completely processed. See SMPOUT to determine the cause of the error.
Note: ERROR does not appear when the CHECK operand is specified on the command.
EXCLUDED: The SYSMOD was specified on the EXCLUDE operand.
HELD: The SYSMOD was held because one or more of HOLD reason IDs were not resolved.
INCMPLT: SYSMOD processing is incomplete because of some failure. No target libraries were updated.
NOGO: The SYSMOD was not processed before any updates. This can happen when a related SYSMOD has an error. See SMPOUT to determine the cause of the error.
NOGO(E): SYSMOD processing stopped because a required SYSMOD was excluded.
NOGO(H): SYSMOD processing stopped because a required SYSMOD was held.
SUPD: The SYSMOD is superseded by one or more SYSMODs being processed. The superseding SYSMODs are shown in the REQUISITE AND SUPBY SYSMODS field.
Note: Not all superseded SYSMODs are listed in the report. For example, SYSMODs that were not selected for processing and appear only in another SYSMOD's ++VER SUP operand are not listed.

TYPE

is the SYSMOD type: APAR, FUNCTION, PTF, or USERMOD. For superseded SYSMODs that have not been received, this field is blank.

FMID

is the function SYSMOD that owns the SYSMOD. For superseded SYSMODs, this field is blank.

REQUISITE SYSMODS, SUPBY SYSMODS, HOLD REASON-IDs, AND CAUSER SYSMODS

lists SYSMODs or reason IDs associated with the SYSMODs being installed. If a SYSMOD was not installed, these SYSMODs or reason IDs are preceded by a character indicating why (-, *, or #). The list of SYSMODs or reason IDs is preceded by one of the following values, which indicate the type of SYSMOD or reason ID.

CAUSER

SYSMODs whose failure led to the failure of the SYSMOD in the SYSMOD field. All the SYSMODs in the CAUSER field are in the Causer SYSMOD Summary report, along with a summary of the related error and, when feasible, a list of possible causes for the error. This holds true even when the SYSMOD in the SYSMOD field and the causer SYSMOD are the same.

HOLDE

ERROR reason IDs for the SYSMOD.

HOLDF

FIXCAT reason IDs for the SYSMOD.

HOLDS

SYSTEM reason IDs for the SYSMOD.

HOLDU

USER reason IDs for the SYSMOD.

IFREQ

Conditional requisites for the SYSMOD, as defined by its associated ++IF statements or, if the SYSMOD is a function, defined by previously processed SYSMODs.

PRE

Prerequisites for the SYSMOD.

REQ

Requisites for the SYSMOD.

SUPBY

SYSMODs that supersede the SYSMOD.

XZIFREQ

For APPLY and ACCEPT processing, these are:
- Conditional requisites for the SYSMOD, as defined by its associated ++IF statements. Cross-zone requisite checking has found that the FMID named on the ++IF exists in another zone.
- Conditional requisites (CIFREQ data) found in other zones for function SYSMODs being installed into the set-to zone.
For RESTORE processing, these are the causer SYSMODs in another zone. Cross-zone requisite checking has found that another SYSMOD (a causer) has named the SYSMOD being restored as a requisite on a ++IF statement.

XZIFREQ is listed as a parenthesized pair of names —for example, (SYSMOD2 ZONE3)— identifying a SYSMOD and the participating cross-zone.

For HOLDE, HOLDS, HOLDU, IFREQ, PRE, REQ, and XZIFREQ:

A dash (–) next to a listed SYSMOD means that SYSMOD has NOGO status and may not be available for processing.
If an asterisk (*) appears next to a listed SYSMOD, that SYSMOD has NOGO status, but the appropriate option was specified in the BYPASS operand list on the APPLY or ACCEPT commands. This means that even if the SYSMOD is not available for processing, the SYSMOD that has specified it as a requisite can be processed.

For SUPBY:

If a pound sign (#) appears next to a listed SYSMOD, that SYSMOD has not been successfully processed. As long as at least one superseding SYSMOD has been successfully processed, the superseded SYSMOD is considered to be installed.