P0 - SYSMOD status record type 0

Status records are created for SYSMODs for which some utility work was done during the command and for SYSMODs superseded by SYSMODs that were successfully applied or restored.

Note: The superseded SYSMODs are included to aid in analyzing when a set of deltas is ready for distribution. When a SYSMOD in ERROR status is noted as superseded in a subsequent delta, it's error status may be considered resolved.
The format and contents of this record type are shown in Table 1.
Table 1. SYSMOD status record type 0
Field name Position (decimal) Length (decimal) Description
Record type 1 2 The characters 'P0'.
SYSMOD ID 3 7 The SYSMOD ID.
Status 10 8 The status of the SYSMOD. The following text may appear in this field. Where the text is less than 8 characters, it is left justified and padded with blanks.
  • APPLIED
  • DELETED
  • ERROR
  • INCMPLT
  • RESTORED
  • SUPD
The status in this library change record is consistent with the status of the SYSMOD as reported in the SYSMOD STATUS REPORT.
Note: SYSMODs identified in the SYSMOD STATUS REPORT with the following status are not included in the library change records, because they failed during SYSMOD selection processing.
  • EXCLUDED
  • HELD
  • NOGO
  • NOGO(E)
  • NOGO(H)
FMID 18 7 The FMID of the SYSMOD. If the status is SUPD and the SYSMOD is not in process, this field contains blanks.
Type 25 8 The SYSMOD type. The following text is valid in this field:
  • FUNCTION
  • PTF
  • APAR
  • USERMOD
If the status is SUPD and the SYSMOD is not in process, this field contains blanks.
The SYSMOD Status (P0) records follow the E0 record in the set of library change records for the command. Figure 1 shows examples of P0 records written for APPLY processing.
Figure 1. Example of SYSMOD status records
         1         2         3         4         5         6         7         8
----+----0----+----0----+----0----+----0----+----0----+----0----+----0----+----0
P0UZ00002ERROR   H000001PTF
P0UZ00001APPLIED H000001PTF
P0UZ00000SUPD

Additionally, fields are added to the header and trailer records to represent the count of SYSMODs represented in the P0 records with each status.

This information tells you whether any errors are contained in the current delta. However, just because a delta is error free, it does not mean that it can be distributed without resolving errors in previous deltas. You must perform the task of error resolution among deltas prior to distribution in order to ensure an error free package. Refer to Usage recommendations for usage information.