Chapter 17. SMF records

The following sections describe each SMF record in detail.

Record type 0 (X'00') — IPL

Record type 0 is written after every SMF initialization. It includes the virtual and central storage sizes and some of the SMF options in effect. See record type 90 (subtype 9) for information about the IPL of SMF.

Record environment

The following conditions exist for the generation of the SMF type 0 record:

Macro
SMFEWTM(1), BRANCH=YES (record exit: IEFU84)

Record mapping

The SMF type 0 record is mapped as follows.

Header/self-defining section

This section contains the common SMF record header fields and, if applicable, the triplet fields (offset/length/number) that locate the other sections on the record.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF0LEN & 2 & binary & Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF0SEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF0FLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved \\
& & & & 3–6 \quad Version indicators* \\
& & & & 7 \quad Reserved. \\
& & & & *See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
5 \quad 5 & SMF0RTY & 1 & binary & Record type 0 (X'00') \\
\hline
6 \quad 6 & SMF0TME & 4 & binary & Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer. \\
\hline
10 \quad A & SMF0DTE & 4 & packed & Date when the record was moved into the SMF buffer, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
14 \quad E & SMF0SID & 4 & EBCDIC & System identification (from the SID parameter). \\
\hline
18 \quad 12 & SMF0JWT & 4 & binary & Limit, in minutes, of continuous wait for the job (taken from JWT parameter). \\
& & & & Continuous wait time is defined as time spent waiting while the application program is in control. For example, for data sets allocated dynamically (while the application program is running, for example) either or both of the following count toward a job's continuous wait time: \\
& & & & • The time required to recall a data set from HSM Migration Levels 1 or 2 \\
& & & & • The time required to mount a tape \\
& & & & If a data set was allocated statically (for a DD statement, for example) these activities will not be counted towards the job's continuous wait time. \\
\hline
22 \quad 16 & SMF0BUF & 4 & binary & This field contains meaningless information. \\
\hline
26 \quad 1A & SMF0VST & 4 & binary & Number of 1K bytes in virtual storage. \\
\hline
30 \quad 1E & SMF0OPT & 1 & binary & SMF options: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad Reserved \\
& & & & 1 \quad Reserved \\
& & & & 2 \quad Reserved. \\
& & & & 3 \quad Data set accounting. Record types selected. This bit is on when one of the following record types is selected: 14, 15, 17, 18, 62, 63, 64, 67 or 68. (See “TYPE and NOTYPE — Selecting and directing SMF records” on page 59.) \\
& & & & 4 \quad Volume accounting. Record types 10 or 69 selected. (See “TYPE and NOTYPE — Selecting and directing SMF records” on page 59.) \\
& & & & 5 \quad Reserved. \\
& & & & 6 \quad Type 17 records will be written for temporary data sets (REC(ALL)). \\
& & & & 7 \quad Reserved. \\
\hline
31 \quad 1F & SMF0RST & 4 & binary & Number of 1K bytes in central storage. \\
& & & & This field is only accurate below 4 TB. For larger systems, this field contains X'FFFFFFFF'. The SMF0RS4K field also represents the system size and is not limited to 4 TB. See SMF0RS4K and SMF0RS4K\_Not\_Valid for additional instructions to determine if SMF0RS4K contains valid information. \\
\hline
35 \quad 23 & SMF0RSV & 1 & & Reserved. \\
\hline
36 \quad 24 & SMF0OSL & 8 & EBCDIC & MVS product name. \\
\hline
44 \quad 2C & SMF0SYN & 8 & EBCDIC & System name (from the SYSNAME parameter in the IEASYSxx parmlib member). \\
\hline
52 \quad 34 & SMF0SYP & 8 & EBCDIC & Sysplex name (from the SYSPLEX parameter in the COUPLExx parmlib member). \\
\hline
60 \quad 3C & SMF0TZ & 4 & binary & Difference in time between local time and Greenwich mean time in binary units of 1.048576 seconds. The value of SMF0TZ is copied from the CVTTZ field. For more information about the CVTTZ field, see the CVT mapping macro in z/OS MVS Data Areas in the z/OS Internet library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary). \\
\hline
64 \quad 40 & SMF0MSWT & 4 & binary & Started task wait time limit (SMFPRMxx SWT(hhmm) value) converted to minutes. \\
\hline
68 \quad 44 & SMF0MTWT & 4 & binary & TSO wait time limit (SMFPRMxx TWT(hhmm) value) converted to minutes. \\
\hline
72 \quad 48 & SMF0TBUF & 2 & binary & The number of megabytes specified by the SMFTBUFF IEASYSxx parmlib option. If the SMFTBUFF parameter value is incorrectly specified or SMFTBUFF is not specified, this value will be zero, and the default buffer size of 5 megabytes was used during IPL SMF initialization processing. \\
\hline
74 \quad 4A & SMF0\_End\_V1 & 0 & n/a & End of version 1. \\
\hline
74 \quad 4A & SMF0RS4K & 8 & binary & Number of 4K frame units in central storage. \\
& & & & If the record length in SMF0LEN is SMF0\_Len\_V2, this field always contains valid information. To determine whether this field contains valid information when the record length in SMF0LEN is SMF0\_Len\_V3 or larger: \\
& & & & • If this field contains a non-zero value, it contains valid information. Also, the SMF0RS4K\_Not\_Valid bit will be off. \\
& & & & • If this field contains a zero value, it does not contain valid information. The SMF0RS4K\_Not\_Valid bit will be on. \\
& & & & It is sufficient to check either the SMF0RS4K field for a non-zero value or the SMF0RS4K\_Not\_Valid bit to determine whether the field contains valid information. This field always contains valid information as of z/OS 2.5. \\
\hline
82 \quad 52 & SMF0\_End\_V2 & 0 & n/a & End of version 2. \\
\hline
82 \quad 52 & SMF0\_Num\_CrypCtrs & 2 & binary & Number of crypto counters supported by this system. \\
\hline
84 \quad 54 & SMF0\_Num\_NNPICtrs & 2 & binary & Number of NNPI counters supported by this system. \\
\hline
86 \quad 56 & SMF0\_Flags & 1 & binary & Flags \\
& & & & \textbf{Bit (Name) \quad Meaning when set} \\
& & & & 0 (SMF0RS4K\_Not\_Valid) \\
& & & & Indicates that SMF0RS4K does not contain a valid value. When this bit is on, SMF0RS4K will contain zeros. See the description of SMF0RS4K for more information. \\
& & & & 1–7 \quad Reserved. \\
\hline
87 \quad 57 & SMF0\_End\_V3 & 0 & n/a & End of version 3. \\
\hline
\end{tabular}

Version information:

When processing a type 0 record, the value in SMF0LEN can be used to determine the version of the record. Equates are provided for the lengths of each version:

Version 1

This version contains the fields through SMF0TBUF. SMF0LEN contains the value SMF0_Len_V1 (X'4A').

Version 2

This version contains the fields through SMF0RS4K. SMF0LEN contains the value SMF0_Len_V2 (X'52').

Version 3

This version contains the fields through SMF0_Flags. SMF0LEN contains the value SMF0_Len_V3 (X'57')

Record type 2 (X'02') — Dump header

The SMF dump program writes record type 2 to the dump data set. It indicates the beginning of a dump of the SMF data set from a direct access device (usually to a tape). There are three variations of this record. If bit 1 at offset 4 is ON, then subtypes are supported; if the bit is OFF, the record consists of the standard SMF record header only.

Record environment

The following conditions exist for the generation of the SMF type 2 record:

Macro
None

Record mapping

The SMF type 2 record is mapped as follows.

Header/self-defining section

This section contains the common SMF record header fields and, if applicable, the triplet fields (offset/length/number) that locate the other sections on the record.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2LEN & 2 & binary & Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF2SEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF2FLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved \\
& & & & 3–6 \quad Version indicators* \\
& & & & 7 \quad Reserved. \\
& & & & *See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
5 \quad 5 & SMF2RTY & 1 & binary & Record type 2 (X'02'). \\
\hline
6 \quad 6 & SMF2TME & 4 & binary & Time since midnight, in hundredths of a second, when the record was moved into the dump data set. \\
\hline
10 \quad A & SMF2DTE & 4 & packed & Date when the record was moved into the dump date set, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
14 \quad E & SMF2SID & 4 & EBCDIC & System identification (from the SID parameter). \\
\hline
\end{tabular}

Subtype 1

This is a signature record that represents a signature group and is consumed for signature verification by the IFASMFDL and IFASMFDP utilities.

The SMF type 2 subtype 1 record is mapped as follows.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2GLEN & 2 & binary & Record length. This field and the next field (total of 4 bytes) form the record descriptor word (RDW). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF2GSEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF2GFLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad Reserved. \\
& & & & 1 \quad Subtypes are valid. \\
& & & & 2–7 \quad Reserved. \\
\hline
5 \quad 5 & SMF2GRTY & 1 & binary & Record type 2 (X'02'). \\
\hline
6 \quad 6 & SMF2GTME & 4 & binary & Time since midnight, in hundredths of a second, of the last record in the group. \\
\hline
10 \quad A & SMF2GDTE & 4 & packed & Date of the last record in the group, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
14 \quad E & SMF2GSID & 4 & EBCDIC & System identification: DUMY \\
\hline
18 \quad 12 & SMF2GWID & 4 & EBCDIC & Subsystem identification. \\
\hline
22 \quad 16 & SMF2GSTP & 2 & binary & Subtype 1 (X'0001'). \\
\hline
24 \quad 18 & SMF2GRSID & 4 & EBCDIC & The group's SID. \\
\hline
28 \quad 1C & SMF2GFLG2 & 1 & binary & Group indicators: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad First group written. \\
& & & & 1 \quad Group's subtype is valid. \\
& & & & 2 \quad When on, this group's type is in SMF2GRTYPX. When off, this group's type is in SMF2GRTYPE. This bit will always be on for records generated on a z/OS 2.3 or later system. \\
& & & & 3 \quad When on, this record was generated on a system where the fix for APAR OA55526 was applied. This bit will always be on for records generated on a z/OS 2.4 or later system. \\
& & & & 4 \quad This record contains a self-defining section. \\
& & & & 5–7 \quad Reserved. \\
\hline
29 \quad 1D & SMF2GRTYPE & 1 & binary & The record type for this group. This field is only filled in when bit 2 of SMF2GFLG2 is off. \\
\hline
30 \quad 1E & SMF2GSTYPE & 2 & binary & The record subtype for this group. \\
\hline
32 \quad 20 & SMF2GFTME & 4 & binary & Time since midnight, in hundredths of a second, of the first record in the group. \\
\hline
36 \quad 24 & SMF2GFDTE & 4 & EBCDIC & Date of the first record in the group, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
40 \quad 28 & SMF2GCNT & 4 & binary & The number of records in this signature group. \\
\hline
44 \quad 2C & SMF2GHASHMETH & 1 & binary & A bit array indicating the hash method used for this group. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad SHA1 \\
& & & & 1 \quad SHA256 \\
& & & & 2 \quad SHA384 \\
& & & & 3 \quad SHA512 \\
& & & & 4–7 \quad Reserved \\
\hline
45 \quad 2D & SMF2GSIGTYPE & 1 & binary & A bit array indicating the signature type used for this group. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad RSA \\
& & & & 1 \quad ECDSA \\
& & & & 2–7 \quad Reserved \\
\hline
46 \quad 2E & SMF2GTOKENNAME & 32 & EBCDIC & The saved CKA\_ID of the PKCS\#11 token name used to generate this signature. \\
\hline
78 \quad 4E & SMF2GRTYPX & 2 & binary & The record type for this group. This field is only filled in when bit 2 of SMF2GFLG2 is on. \\
\hline
80 \quad 50 & SMF2GSIGLEN & 4 & binary & The digital signature length for this signature group \\
\hline
84 \quad 54 & SMF2GSIG & varies & EBCDIC & The digital signature for this signature group. It is the result of the hash and sign operation (using the hash method and signature type specified in this record) on the concatenation of the following: \\
& & & & 1. Running hashsum of all the previous group's records (hash each entire record padded out to a 128-byte boundary with zeros). This will be zeros for the first group within an SMF interval. \\
& & & & 2. Running hashsum of all this group's records (hash each entire record padded out to a 128-byte boundary with zeros). \\
& & & & The length of this signature is contained in SMF2GSIGLEN. \\
& & & & Note: For hashsums generated with the SHA-384 hash method, each hashsum is 48 bytes of data padded with 16 bytes of zeros. \\
\hline
\end{tabular}

Subtype 1 - Self-defining section

This section contains the triplet fields (offset, length, and number) that locate other sections in the record. This triplet information should be checked prior to accessing a section of the record. The "number" triplet field is the primary indication of the existence of the section. This section is an extension of the header and physically follows it in the record. It is located at the offset of SMF2GSIG (84 or X'54') plus the length of the digital signature, found in SMF2GSIGLEN. The self-defining section is present only when bit 4 in the SMF2GFLG2 field in the header is on.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2GSDSLEN & 2 & binary & Length of the self-defining section. \\
\hline
2 \quad 2 & * & 2 & binary & Reserved. \\
\hline
4 \quad 4 & SMF2GSDSASignOffset & 4 & binary & Offset from the beginning of the record, including the record descriptor word (RDW), to the start of the first ARECSIGN section. \\
\hline
8 \quad 8 & SMF2GSDSASignLen & 2 & binary & Length of ARECSIGN section. \\
\hline
10 \quad A & SMF2GSDSASignNum & 2 & binary & Number of ARECSIGN sections. \\
\hline
\end{tabular}

Subtype 1 - ARECSIGN section

This section contains the alternate signature information. This section is present only when ARECSIGN is in effect at the time the record is generated.

Triplet information: This section is located using the following triplet fields which are located in the self-defining section.

Offset:
SMF2GSDSASignOffset

Length:
SMG2GSDSASignLen

Number:
SMF2GSDSASignNum. This field contains 0 if no ARECSIGN section is present, or non-zero if at least one ARECSIGN section is present.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2GASignHashMeth & 1 & binary & A bit array indicating the alternate signature hash method for this group. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved \\
& & & & 3 \quad SHA512 \\
& & & & 4–7 \quad Reserved \\
\hline
1 \quad 1 & SMF2GASignSigType & 1 & binary & A bit array indicating the alternate signature type used for this group. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–1 \quad Reserved \\
& & & & 2 \quad LI2 \\
& & & & 3–7 \quad Reserved \\
\hline
2 \quad 2 & SMF2GASignTokenName & 32 & EBCDIC & The saved CKA\_ID of the PKCS\#11 token name used to generate this signature. \\
\hline
34 \quad 22 & * & 2 & binary & Reserved. \\
\hline
36 \quad 24 & SMF2GASignSigLen & 4 & binary & The length of the alternate digital signature for this signature group. \\
\hline
40 \quad 28 & SMF2GASignSig & varies & EBCDIC & The digital signature for this signature group. The length of this field is in SMF2GASignSigLen. \\
\hline
\end{tabular}

Subtype 2

This is a signature record that represents a signature interval and is consumed for signature verification by the IFASMFDL and IFASMFDP utilities.

The SMF type 2 subtype 2 record is mapped as follows.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2ILEN & 2 & binary & Record length. This field and the next field (total of 4 bytes) form the record descriptor word (RDW). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF2ISEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF2IFLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad Reserved. \\
& & & & 1 \quad Subtypes are valid. \\
& & & & 2–7 \quad Reserved. \\
\hline
5 \quad 5 & SMF2IRTY & 1 & binary & Record type 2 (X'02'). \\
\hline
6 \quad 6 & SMF2ITME & 4 & binary & Time since midnight, in hundredths of a second, of the interval. \\
\hline
10 \quad A & SMF2IDTE & 4 & packed & Date of the interval, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
14 \quad E & SMF2ISID & 4 & EBCDIC & System identification: DUMY \\
\hline
18 \quad 12 & SMF2IWID & 4 & EBCDIC & Subsystem identification. \\
\hline
22 \quad 16 & SMF2ISTP & 2 & binary & Subtype 2 (X'0002'). \\
\hline
24 \quad 18 & SMF2IRSID & 4 & EBCDIC & The interval's SID. \\
\hline
28 \quad 1C & SMF2IFLG2 & 1 & binary & Interval indicators: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad First interval written. \\
& & & & 1 \quad Interval's subtype is valid. \\
& & & & 2 \quad This interval is the result of a HALT. \\
& & & & 3 \quad This interval contains new cryptography options. \\
& & & & 4 \quad When on, this interval's type is in SMF2IRTYPX. When off, this interval's type is in SMF2IRTYPE. This bit will always be on for records generated on a z/OS 2.3 or later system. \\
& & & & 5 \quad This is a "close interval" that occurs at midnight of the end of day. \\
& & & & 6 \quad This record was generated on a system where the fix for APAR OA55526 was applied. This bit will always be on for records generated on a z/OS 2.4 or later system. \\
& & & & 7 \quad When on, this record contains a self-defining section. \\
\hline
29 \quad 1D & SMF2IRTYPE & 1 & binary & The record type for this interval. This field is only filled in when bit 4 of SMFIGFLG2 is off. \\
\hline
30 \quad 1E & SMF2ISTYPE & 2 & binary & The record subtype for this interval. \\
\hline
32 \quad 20 & SMF2IFTME & 4 & binary & Time since midnight, in hundredths of a second, of the first record in the interval. \\
\hline
36 \quad 24 & SMF2IFDTE & 4 & EBCDIC & Date of the first record in the interval, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
40 \quad 28 & SMF2ILTME & 4 & binary & Time since midnight, in hundredths of a second, of the last record in the interval. \\
\hline
44 \quad 2C & SMF2ILDTE & 4 & EBCDIC & Date of the last record in the interval, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
48 \quad 30 & SMF2INTME & 4 & binary & Time since midnight, in hundredths of a second, of the next interval. \\
\hline
52 \quad 34 & SMF2INDTE & 4 & EBCDIC & Date of the next interval, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
56 \quad 38 & SMF2ICNT & 4 & binary & The number of records in this signature interval. \\
\hline
60 \quad 3C & SMF2IHASHMETH & 1 & binary & A bit array indicating the hash method used for this interval. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad SHA1 \\
& & & & 1 \quad SHA256 \\
& & & & 2 \quad SHA384 \\
& & & & 3 \quad SHA512 \\
& & & & 4–7 \quad Reserved \\
\hline
61 \quad 3D & SMF2ISIGTYPE & 1 & binary & A bit array indicating the signature type used for this interval. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad RSA \\
& & & & 1 \quad ECDSA \\
& & & & 2–7 \quad Reserved \\
\hline
62 \quad 3E & SMF2ITOKENNAME & 32 & EBCDIC & The saved CKA\_ID of the PKCS\#11 token name used to generate this signature. \\
\hline
94 \quad 5E & SMF2IRTYPX & 2 & binary & The record type for this interval. This field is only filled in when bit 4 of SMFIGFLG2 is on. \\
\hline
96 \quad 60 & SMF2ISIGLEN & 4 & binary & The digital signature length for this signature interval. \\
\hline
100 \quad 64 & SMF2ISIG & varies & EBCDIC & The digital signature for this signature interval. It is the result of the hash and sign operation (using the hash method and signature type specified in this record) on the concatenation of the following: \\
& & & & 1. Hash of the previous interval record's data, from the beginning of the record up to, but not including, the SMF2ISIGLEN field. This will contain zeros for the first interval after signature processing is enabled. \\
& & & & 2. Running hashsum of all this group's records (hash each entire record padded out to a 128-byte boundary with zeros). This will contain zeros if this interval did not contain any groups. \\
& & & & 3. Hash of this interval record's data, from the beginning of the record up to, but not including, the SMF2ISIGLEN field. \\
& & & & The length of this signature is contained in SMF2ISIGLEN. \\
& & & & Note: For hashsums generated with the SHA-384 hash method, each hashsum is 48 bytes of data padded with 16 bytes of zeros. \\
\hline
\end{tabular}

Subtype 2 - Self-defining section

This section contains the triplet fields (offset, length, and number) that locate other sections in the record. This triplet information should be checked prior to accessing a section of the record. The "number" triplet field is the primary indication of the existence of the section. This section is an extension of the header and physically follows it in the record. It is located at the offset of SMF2ISIG (100 or X'64') plus the length of the digital signature in SMF2ISIGLEN. The self-defining section is present only when bit 7 in the SMF2IFLG2 field in the header is on.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2ISDSLEN & 2 & binary & Length of the self-defining section. \\
\hline
2 \quad 2 & * & 2 & binary & Reserved. \\
\hline
4 \quad 4 & SMF2ISDSASignOffset & 4 & binary & Offset from the beginning of the record, including the record descriptor word (RDW), to the start of the first ARECSIGN section. \\
\hline
8 \quad 8 & SMF2ISDSASignLen & 2 & binary & Length of ARECSIGN section. \\
\hline
10 \quad A & SMF2ISDSASignNum & 2 & binary & Number of ARECSIGN sections. \\
\hline
\end{tabular}

Subtype 2 - ARECSIGN section

This section contains the alternate signature information. This section is present only when ARECSIGN is in effect at the time the record is generated.

Triplet information: This section is located using the following triplet fields which are located in the self-defining section.

Offset:
SMF2ISDSASignOffset

Length:
SMF2ISDSASignLen

Number:
SMF2ISDSASignNum. This field contains 0 if no ARECSIGN section is present, or non-zero if at least one ARECSIGN section is present.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF2IASignHashMeth & 1 & binary & A bit array indicating the alternate signature hash method for this interval. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved \\
& & & & 3 \quad SHA512 \\
& & & & 4–7 \quad Reserved \\
\hline
1 \quad 1 & SMF2IASignSigType & 1 & binary & A bit array indicating the alternate signature type used for this interval. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–1 \quad Reserved \\
& & & & 2 \quad LI2 \\
& & & & 3–7 \quad Reserved \\
\hline
2 \quad 2 & SMF2IASignTokenName & 32 & EBCDIC & The saved CKA\_ID of the PKCS\#11 token name used to generate this signature. \\
\hline
34 \quad 22 & SMF2IASignFlgs & 1 & binary & Alternate signature indicators. \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad This interval contains new cryptography options. \\
& & & & 1–7 \quad Reserved. \\
\hline
35 \quad 23 & * & 1 & binary & Reserved. \\
\hline
36 \quad 24 & SMF2IASignSigLen & 4 & binary & The length of the alternate digital signature for this signature interval. \\
\hline
40 \quad 28 & SMF2IASignSig & varies & EBCDIC & The digital signature for this signature interval. The length of this field is in SMF2IASignSigLen. \\
\hline
\end{tabular}

Record type 3 (X'03') — Dump trailer

The SMF dump program writes record type 3 to the dump data set. This record consists of the standard SMF record header only. It marks the end of a dump of the SMF data set from a direct access device (usually to a tape).

Record environment

The following conditions exist for the generation of the SMF type 3 record:

Macro
None

Record mapping

The SMF type 3 record is mapped as follows.

Header/self-defining section

This section contains the common SMF record header fields and, if applicable, the triplet fields (offset/length/number) that locate the other sections on the record.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF3LEN & 2 & binary & Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF3SEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF3FLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved \\
& & & & 3–6 \quad Version indicators* \\
& & & & 7 \quad Reserved. \\
& & & & *See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
5 \quad 5 & SMF3RTY & 1 & binary & Record type 3 (X'03'). \\
\hline
6 \quad 6 & SMF3TME & 4 & binary & Time since midnight, in hundredths of a second, when the record was moved into the dump data set. \\
\hline
10 \quad A & SMF3DTE & 4 & packed & Date when the record was moved into the dump data set, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
14 \quad E & SMF3SID & 4 & EBCDIC & System identification (from the SID parameter). \\
\hline
\end{tabular}

Record type 4 (X'04') — Step termination

Record type 4 is written at the normal or abnormal termination of a job step for a background job, or when a job step is flushed during or after job initiation. It is not written for a job step that follows a CANCEL operator command.

Note: IBM recommends that you use record type 30 rather than record types 4, 5, 20, 34, 35, and 40. Use of record type 4 may cause you to miss key workload indicators.

This record identifies the job step by the job log identification, step name, number of the step within the job, user identification, program name and performance group number. The job name, time, and date that the reader recognized the JOB card (for this job) constitute the job log identification. If accounting numbers (which can be alphameric) were specified in the EXEC statement, they are included.

This record also contains operating information such as:

• The job step start and end times
• Step CPU time
• Step service
• Step termination status
• Number of records in DD DATA and DD* data sets (processed by the step)
• Device allocation start time
• Problem program start time
• Storage protect key.

It contains the number of page-ins, page-outs, swap-ins, and swap-outs for both VIO and non-VIO data sets.

Record type 4 has an entry for each non-spooled data set that was defined by a DD statement. Each entry lists the device class, unit type, channel address, unit address, and EXCP count for the data set. Data sets are usually recorded in the order of the step DD statements; they are not identified by name. (An installation written IEFUJV exit routine can record this order as each statement is validated). Dynamic allocation or deallocation can affect the order. For data sets that are dynamically unallocated, the data set entry information is in record type 40 — not record type 4.

When the TIOT size is greater than 32K (more than 1635 DD statements), device data is not collected for the type 4 record. The data is available in the type 30 record.

The record contains information on service and transaction active timer. For information on service and transaction time, see z/OS MVS Initialization and Tuning Guide. For more information on EXCP count and CPU time, see Chapter 10, “EXCP count,” on page 119 and Chapter 11, “CPU time,” on page 121.

Record environment

The following conditions exist for the generation of the SMF type 4 record:

Macro
SMFEWTM(1), BRANCH=YES (record exit: IEFU84)

Record mapping

The SMF type 4 record is mapped as follows.

Header/self-defining section

This section contains the common SMF record header fields and, if applicable, the triplet fields (offset/length/number) that locate the other sections on the record.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF4LEN & 2 & binary & Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF4SEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF4FLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved \\
& & & & 3–6 \quad Version indicators (see “Standard and extended SMF record headers” on page 164 for details.) \\
& & & & 7 \quad Reserved. \\
\hline
5 \quad 5 & SMF4RTY & 1 & binary & Record type 4 (X'04'). \\
\hline
6 \quad 6 & SMF4TME & 4 & binary & Time since midnight, in hundredths of a second, that the record is passed to the SMF writer. This is the time when the step terminated. \\
\hline
10 \quad A & SMF4DTE & 4 & packed & Date when the record is passed to the SMF writer, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. This is the date when the step terminated. \\
\hline
14 \quad E & SMF4SID & 4 & EBCDIC & System identification (from the SID parameter). \\
\hline
18 \quad 12 & SMF4JBN & 8 & EBCDIC & Job name. The job name, time, and date that the reader recognized the JOB card (for this job) constitute the job log identification, or transaction name (for APPC output). \\
\hline
26 \quad 1A & SMF4RST & 4 & binary & Time since midnight, in hundredths of a second, that the reader recognized the JOB card (for this job). \\
\hline
30 \quad 1E & SMF4RSD & 4 & packed & Date when the reader recognized the JOB card (for this job), in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
34 \quad 22 & SMF4UIF & 8 & EBCDIC & User-defined identification field (taken from common exit parameter area, not from USER=parameter on job statement). \\
\hline
42 \quad 2A & SMF4STN & 1 & binary & Step number (first step = 1, and so on). \\
\hline
43 \quad 2B & SMF4SIT & 4 & binary & Time since midnight, in hundredths of a second, that the initiator selected this step. \\
\hline
47 \quad 2F & SMF4STID & 4 & packed & Date when the initiator selected this step, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
51 \quad 33 & SMF4NCI & 4 & binary & Number of card-image records in DD DATA and DD* data sets read by the reader for the step. \\
\hline
55 \quad 37 & SMF4SCC & 2 & binary & Step completion code: \\
& & & & X'0ccc' indicates system ABEND in the job step where ccc is the system ABEND code. (See z/OS MVS System Codes.) \\
& & & & X'8ccc' indicates user ABEND in the job step where ccc is the user ABEND code. \\
& & & & X'nnnn' indicates normal completion where nnnn is the contents of the two low-order bytes in register 15 at termination. \\
& & & & X'0000' indicates either \\
& & & & 1. The job step was flushed (not processed) because of an error during allocation or in a preceding job step, or \\
& & & & 2. normal job completion with a return code of zero. \\
& & & & Use this field in conjunction with the step termination indicator field (offset 87). \\
\hline
57 \quad 39 & SMF4PRTY & 1 & binary & Address space dispatching priority (taken from DPRTY= parameter on EXEC statement or the default APG value). For more information see z/OS MVS Initialization and Tuning Guide. \\
\hline
58 \quad 3A & SMF4PGMN & 8 & EBCDIC & Program name (taken from PGM= parameter on EXEC card). If a backward reference was used, then this field contains *.DD. \\
\hline
66 \quad 42 & SMF4STMN & 8 & EBCDIC & Step name (taken from name on the EXEC statement). \\
\hline
74 \quad 4A & SMF4RSV5 & 2 & binary & Reserved. SMF4RSH0, formerly a two-byte field at this offset, has been increased to four bytes and moved to offset 82. \\
\hline
76 \quad 4C & SMF4SYST & 2 & binary & Largest amount of storage used from top of private area, in 1K units. This storage area includes the LSQA and SWA (subpools 229, 230, 236, 237, 249, and 253-255). If ADDRSPC=REAL is specified, this field equals the amount of storage used that was not from the contiguous central storage reserved for the program. See offsets 82 and 102. If storage was not allocated (job step was flushed), these fields equal zero. \\
\hline
78 \quad 4E & SMF4HOST & 2 & binary & Largest amount of storage from bottom of private area, in 1K units. This storage area includes subpools 0–127, 129–132, 244, 251 and 252. If ADDRSPC=REAL is specified, this field equals the amount of contiguous central storage that was used. See offsets 82 and 102. \\
\hline
80 \quad 50 & SMF4RV1 & 2 & & Reserved. \\
\hline
82 \quad 52 & SMF4RSH0 & 4 & binary & Region size established, in 1K units taken from the REGION parameter in the JCL, and rounded up to a 4K boundary. If ADDRSPC=REAL is specified, this field equals the amount of contiguous central storage reserved for the program. If the region requested was greater than 16 megabytes, the region established resides above 16 megabytes, and this field will contain a minimum value of 32 megabytes. \\
\hline
86 \quad 56 & SMF4SPK & 1 & binary & Storage protect key, in the form xxxx0000 (where xxxx is the key). \\
\hline
87 \quad 57 & SMF4STI & 1 & binary & Step termination indicator \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0 \quad Reserved \\
& & & & 1 \quad Canceled by exit IEFUJV \\
& & & & 2 \quad Canceled by exit IEFUJI \\
& & & & 3 \quad Canceled by exit IEFUSI \\
& & & & 4 \quad Canceled by exit IEFACTRT \\
& & & & 5 \quad Step is to be restarted \\
& & & & 6 \quad If 0, normal completion. If 1, ABEND. If step completion code (offset 55) equals 0322 or 0522, IEFUTL allowed the abend to occur. If step completion code equals 0722, IEFUSO allowed the abend to occur. \\
& & & & 7 \quad If 0, normal completion. If 1, step was flushed. \\
\hline
88 \quad 58 & SMF4RV2 & 2 & & Reserved. \\
\hline
90 \quad 5A & SMF4AST & 4 & binary & Device allocation start time, in hundredths of a second. \\
\hline
94 \quad 5E & SMF4PPST & 4 & binary & Problem program start time, in hundredths of a second. \\
\hline
98 \quad 62 & SMF4RV3 & 1 & binary & Reserved. \\
\hline
99 \quad 63 & SMF4SRBT & 3 & binary & Step CPU time under SRBs, in hundredths of a second. This field includes the CPU time for various supervisory routines that are dispatched from SRBs: locking routines, page resolution, swap control, cross-memory communications (WAIT, POST, I/O POST), and TQE scheduling. \\
\hline
102 \quad 66 & SMF4RIN & 2 & binary & Record indicator \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–3 \quad Reserved \\
& & & & 4 \quad Field SMF4SETM is not valid. An overflow condition occurs when the length of the value for the step CPU time under TCBs is greater than 3 bytes. In this case, the step CPU time under TCBs is not recorded in the type 4 record (SMF4SETM); The value is available in the type 30 record (SMF30CPT). If your installation uses an accounting program that does not use the type 30 record to gather step CPU time, you must update that program. Only the type 30 record should be considered valid. \\
& & & & 5 \quad Device data not recorded. When the TIOT size is greater than 32K (more than 1635 DD statements), device data is not collected for the type 4 record. The data is available in the type 30 record. \\
& & & & 6 \quad EXCP count might be wrong. For more information on EXCP count, see Chapter 10, “EXCP count,” on page 119. \\
& & & & 7 \quad If 0, storage is virtual. If 1, storage is central (real). \\
& & & & 8–15 \quad Reserved. \\
\hline
104 \quad 68 & SMF4RLCT & 2 & binary & Offset from the beginning of the record (SMF4FLG) header to the relocate section. The displacement depends upon the size of the accounting fields and the number of devices. \\
\hline
106 \quad 6A & SMF4LENN & 2 & binary & Length of device entry portion of record. Equals: (8 times the number of devices) + 2 \\
\hline
\end{tabular}

Device data section

For each device assigned to each non-spooled data set, there is an eight-byte entry with the following format:

Note: When the TIOT size is greater than 32K (more than 1635 DD statements), device data is not collected for the type 4 record. The data is available in the type 30 record.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF4EXPS & 8 & structure & Data set access information. \\
& & & & Note: Virtual I/O devices are identified by the following: \\
& & & & \textbf{Device class} \quad 0 \\
& & & & \textbf{Unit type} \quad 0 \\
& & & & \textbf{Device number} \quad X'7FFF' \\
& & & & It is important to understand the following: \\
& & & & Allocation messages for VIO data sets will show VIO ALLOCATED TO ddname. \\
& & & & SMF records will show VIO unit addresses as X'7FFF'. \\
& & & & The actual in-storage UCB built for VIO will show address X'3FFF'. \\
& & & & For example, the messages: \\
& & & & • IEF237I X'3FFF' ALLOCATED TO ddname \\
& & & & • IEF237I X'7FFF' ALLOCATED TO ddname \\
& & & & indicate that ddname is not allocated to a Virtual I/O device, but is instead allocated to a real device whose unit address is X'3FFF' or X'7FFF' respectively. \\
\hline
0 \quad 0 & SMF4DEVC & 1 & binary & Device class. \\
\hline
1 \quad 1 & SMF4UTYP & 1 & binary & Unit type. \\
\hline
2 \quad 2 & SMF4CUAD & 2 & binary & Device number. \\
\hline
4 \quad 4 & SMF4EXCP & 4 & binary & EXCP count (see offset 102). \\
\hline
\end{tabular}

Accounting section

After the device entries are the following fields:

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF4LNTH & 1 & binary & Length of accounting section, excluding this field. \\
\hline
1 \quad 1 & SMF4SETM & 3 & binary & Step CPU time under TCBs, in hundredths of a second. This field includes the CPU time for all tasks that are dispatched from TCBs below the level of RCT. CPU time is not expected to be constant between different runs of the same job step. For more information on CPU time, see Chapter 11, “CPU time,” on page 121. \\
\hline
4 \quad 4 & SMF4NAF & 1 & binary & Number of accounting fields. \\
\hline
5 \quad 5 & SMF4ACTF & variable & EBCDIC & Accounting fields. Each entry for an accounting field contains the length of the field (one byte, binary) followed by the field (EBCDIC). A zero indicates an omitted field. \\
\hline
\end{tabular}

Relocate section

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF4PGIN & 4 & binary & Number of non-VIO, non-swap page-ins for this step. This field includes page-ins that are required through page faults, specific page requests, and page fixes. It does not include page reclaims, page-ins for VIO data sets, pages that are swapped in, and page-ins for the common area. \\
\hline
4 \quad 4 & SMF4PGOT & 4 & binary & Number of non-VIO, non-swap page-outs for this step. This field includes page-outs required through page requests, including those pages stolen by the paging supervisor through infrequent use. It does not include page-outs for VIO data sets, pages that are swapped out, and page-outs for the common area. \\
\hline
8 \quad 8 & SMF4NSW & 4 & binary & Number of address space swap sequences. (A swap sequence consists of an address space swap-out and swap-in.) \\
\hline
12 \quad C & SMF4PSI & 4 & binary & Number of pages swapped in. This field includes: LSQA, fixed pages, and those pages that the real storage manager determined to be active when the address space was swapped in. It does not include page reclaims nor pages found in storage during the swap-in process (such as pages brought in from SRBs started after completion of swap-in Stage 1 processing). \\
\hline
16 \quad 10 & SMF4PSO & 4 & binary & Number of pages swapped out. This field includes: LSQA, private area fixed pages, and private area non-fixed changed pages. \\
\hline
20 \quad 14 & SMF4VPI & 4 & binary & Number of VIO page-ins for this step. This field includes page-ins resulting from page faults or specific page requests on a VIO window. It does not include VIO swap-ins or page-ins for the common area. \\
\hline
24 \quad 18 & SMF4VPO & 4 & binary & Number of VIO page-outs for this step. This field includes page-outs resulting from specific page requests on a VIO window, and also those pages stolen by the paging supervisor through infrequent use. It does not include VIO swap-outs or page-outs for the common area. \\
\hline
28 \quad 1C & SMF4SST & 4 & binary & Step service, in service units. This field equals: total job service minus the accumulated job service before this step's initialization. \\
\hline
32 \quad 20 & SMF4ACT (SMF4TAT) & 4 & binary & Step transaction active time, in 1024-microsecond units equal: total job transaction active time minus the accumulated transaction active time before this step's initialization. \\
\hline
36 \quad 24 & SMF4PGNO & 2 & binary & Step performance group number (taken from PERFORM= parameter on JOB or EXEC statement or the RESET operator command). \\
\hline
38 \quad 26 & SMF4TRAN & 4 & binary & Step transaction residency time in 1024-microsecond units. That is the time the transaction was in central storage. \\
\hline
42 \quad 2A & SMF4CPM & 4 & binary & Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted. \\
\hline
46 \quad 2E & SMF4RCLM & 4 & binary & Number of VIO reclaims for this step. \\
\hline
50 \quad 32 & SMF4CPGN & 4 & binary & Number of common area page-ins for this step (LPA+CSA). \\
\hline
54 \quad 36 & SMF4HSPI & 4 & binary & Number of hiperspace page-ins from auxiliary to processor storage. \\
\hline
58 \quad 3A & SMF4PGST & 4 & binary & Number of pages stolen from the storage for this step. \\
\hline
62 \quad 3E & SMF4PSEC & 8 & binary & Number of page seconds for this step, in page millisecond units. Equals: the number of pages used by this step times the processing time it held that number of pages. \\
\hline
70 \quad 46 & SMF4LPAI & 4 & binary & Number of link pack area page-ins for the step. \\
\hline
74 \quad 4A & SMF4HSPO & 4 & binary & Number of hiperspace page-outs from processor to auxiliary storage. \\
\hline
78 \quad 4E & SMF4CPUS & 4 & binary & Step CPU service, in service units. \\
\hline
82 \quad 52 & SMF4IOCS & 4 & binary & Step I/O service, in service units. \\
\hline
86 \quad 56 & SMF4MSOS & 4 & binary & Step main storage service, in service units. \\
\hline
90 \quad 5A & SMF4SRBS & 4 & binary & Step SRB service, in service units. \\
\hline
94 \quad 5E & SMF4RSV1 & 8 & * & Reserved. \\
\hline
\end{tabular}

Record type 5 (X'05') — Job termination

Record type 5 is written at the normal or abnormal termination of a background job.

Note: IBM recommends that you use record type 30 rather than record types 4, 5, 20, 34, 35, and 40. Use of record type 5 may cause you to miss key workload indicators.

This record identifies the job by job log identification, user identification, priority, input class, and programmer's name. If accounting numbers (which can be alphameric) were specified in the JOB statement, they are included. The job name, time, and date that the reader recognized the Job card (for this job) constitute the job log identification. If the job that is terminating is ‘JES2’ or ‘JES3’ then these might be set to zero.

This record also contains operating information such as:

• The job step start and end times
• Number of steps in the job
• Number of records in DD DATA and DD* data sets (processed by the job)
• Job termination status
• Device class
• Unit type
• Storage protect key
• Job service and job CPU time (the job CPU time equals the sum of the job step times).

When a step in a multi-step job terminates abnormally, the subsequent steps, whether processed or flushed, do not propagate the step abend code for processing by this record. The code appears in the step termination record (type 4). Offset 55, can contain X'nnnn' or X'0000' (the job termination indicator (offset 65, bit 6) is set to 1 if an abend occurred in the job).

For more information on service, transaction active time, and performance group number see z/OS MVS Initialization and Tuning Guide. For more information on EXCP count and CPU time, see Chapter 10, “EXCP count,” on page 119 and Chapter 11, “CPU time,” on page 121 respectively.

Record environment

The following conditions exist for the generation of the SMF type 5 record:

Macro
SMFEWTM(1), BRANCH=YES (record exit: IEFU84)

Record mapping

The SMF type 5 record is mapped as follows.

Header/self-defining section

This section contains the common SMF record header fields and, if applicable, the triplet fields (offset/length/number) that locate the other sections on the record.

\begin{tabular}{|cccll|}
\hline
\textbf{Offsets} & \textbf{Name} & \textbf{Length} & \textbf{Format} & \textbf{Description} \\
\hline
0 \quad 0 & SMF5LEN & 2 & binary & Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
2 \quad 2 & SMF5SEG & 2 & binary & Segment descriptor (see record length field). \\
\hline
4 \quad 4 & SMF5FLG & 1 & binary & System indicator: \\
& & & & \textbf{Bit \quad Meaning when set} \\
& & & & 0–2 \quad Reserved. \\
& & & & 3–6 \quad Version indicators (see “Standard and extended SMF record headers” on page 164 for details). \\
& & & & 7 \quad Reserved. \\
\hline
5 \quad 5 & SMF5RTY & 1 & binary & Record type 5 (X'05'). \\
\hline
6 \quad 6 & SMF5TME & 4 & binary & Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer. \\
\hline
10 \quad A & SMF5DTE & 4 & packed & Date when the record is passed to the SMF writer, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. This is the date that the job terminated. \\
\hline
14 \quad E & SMF5SID & 4 & EBCDIC & System identification (from the SID parameter). \\
\hline
18 \quad 12 & SMF5JBN & 8 & EBCDIC & Job name. The job name, time, and date that the reader recognized the JOB statement (for this job) constitute the job log identification, or transaction name (for APPC output). \\
\hline
26 \quad 1A & SMF5RST & 4 & binary & Time since midnight, in hundredths of a second, that the reader recognized the JOB statement (for this job). \\
\hline
30 \quad 1E & SMF5RSD & 4 & packed & Date when the reader recognized the JOB statement (for this job), in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
34 \quad 22 & SMF5UIF & 8 & EBCDIC & User-defined identification field (taken from common exit parameter area, not from USER=parameter on the JOB statement). \\
\hline
42 \quad 2A & SMF5NST & 1 & binary & Number of steps in the job. \\
\hline
43 \quad 2B & SMF5JIT & 4 & binary & Time since midnight, in hundredths of a second, that the initiator selected the job. \\
\hline
47 \quad 2F & SMF5JID & 4 & packed & Date when the initiator selected the job, in the form 0cyydddF. See “Standard and extended SMF record headers” on page 164 for a detailed description. \\
\hline
51 \quad 33 & SMF5NCI & 4 & binary & Number of card-image records in DD DATA and DD* data sets read by the reader for the job. \\
\hline
55 \quad 37 & SMF5JCC & 2 & binary & Job completion code: \\
& & & & X'0ccc' indicates system ABEND in the last job step where ccc is the system ABEND code (see z/OS MVS System Codes). \\
& & & & X'8ccc' indicates user ABEND in the last job step where ccc is the user ABEND code. \\
& & & & X'nnnn' indicates normal completion where nnnn is the contents of the two low-order bytes in register 15 at termination. \\
& & & & X'0000' indicates either (see note): \\
& & & & 1. The last job step was flushed (not processed) because of an error during allocation or in a preceding job step, or \\
& & & & 2. normal job completion with a return code of 0. \\
& & & & \textbf{Note:} When a step in a multi-step job terminates abnormally, the subsequent steps, whether executed or flushed, do not propagate the step abend code for processing this record. The code appears in the job termination record (type 4). In this case, the field - SMF5JCC, can contain X'nnnn'. If an abend occurred in the job, the job termination indicator (bit 6 in the SMF5JBTI field) is set to 1. \\
& & & & Use this field in conjunction with the job termination indicator field, SMFJBTI. \\
\hline
57 \quad 39 & SMF5JPTY & 1 & binary & Job selection priority. This field normally equals the user-assigned priority of zero to 13, but if the job fails while being scheduled, this field equals 14 (taken from the PRTY parameter on the JOB statement). If no value is specified for the PRTY parameter on the JOB statement, this field contains: \\
& & & & • For JES3, the default priority specified on the JES3 STANDARDS initialization statement \\
& & & & • For JES2, a zero. \\
& & & & Note that JES2 does not use the priority value reported in this field. \\
\hline
\end{tabular}