SMF Type 34 Record
This table shows the record layout for type 34 SMF records
It's easy to report on SMF 34 data!
Spectrum SMF Writer handles the difficult SMF record parsing for you automatically. You just specify which fields you want to see.
Spectrum SMF Writer also converts the arcane date and time fields and reformats them into an attractive report.
Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard SMF Record Header” on page 13-1 for a detailed description.
Segment descriptor (see record length field).
System indicator: Bit Meaning When Set 0-2 Reserved 3-6 Version indicators* 7 Reserved.*See “Standard SMF Record Header” on page 13-1 for a detailed description.
Record type 34 (X'22').
Time since midnight, in hundredths of a second, that the record is passed to the SMF writer. This is the time the step ended.
Date when the record was moved into the SMF buffer, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description. This is the date the step ended.
System identification (from the SID parameter).
Logon time, in hundredths of a second.
Logon date, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
User-defined identification field (taken from common exit parameter area, not from USER=parameter on job statement).
Step number (this field always equals 1).
Time since midnight, in hundredths of a second, that the initiator selected this step.
Number of lines of terminal output, that is, number of TPUTs issued.
Number of lines of terminal input, that is, number of TGETs satisfied.
Step completion code: X'0ccc' indicates system ABEND where ccc is the system ABEND code. (See z/OS MVS System Codes.) X'8ccc' indicates user ABEND where ccc is the user ABEND code. X'nnn' indicates normal completion where nnn is the contents of the two low-order bytes in register 15 at end. X'000' indicates either: (1) the job step was flushed (not processed) because of an error during allocation, or (2) normal job completion with a return code of 0. Use this field in conjunction with the step-termination indicator field (offset 87).
Address space dispatching priority (taken from DPTRTY=parameter on the EXEC card or the default APG value).
Program name (taken from PGM=parameter on EXEC card). If a backward reference was used, then this field contains *.DD.
Step name (taken from name on EXEC card).
Note that SMF34TIVEFRGN, formerly a two-byte field at this offset, has been increased to four bytes and moved to offset 82.
Largest amount of storage used from top of private area, in 1K units. This storage area includes the local system queue area (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 this contiguous real storage reserved for the program. See offsets 82 and 102.
Largest amount of storage used from bottom of private area, in 1K units. This storage area includes sub-pool 0-127, 129-132, 244, 251 and 252. If ADDRSPC=REAL is specified, this field equals the amount of contiguous real storage that was used. See offsets 82 and 102. If storage was not allocated (job step was flushed), these fields equal zero.
Region size established, in 1K units taken from the REGION=parameter in the JCL, and rounded up to a four K boundary. If ADDRSPC=REAL is specified, this field equals the amount of contiguous real 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.
Storage protect key, in the form xxxx0000 where xxxx is the key.
Step termination indicator Bit Meaning When Set 0 Reserved. 1 Canceled by exit IEFUJV. 2 Canceled by exit IEFUJI. Job steps canceled by IEFUJI and IEFUSI will not be processed; therefore bit 7 will be on. 3 Canceled by exit IEFUSI Job steps canceled by IEFUJI and IEFUSI will not be processed; therefore bit 7 will be on. 4 Reserved 5 Step is to be restarted. 6 If zero, then normal completion. If 1, then and abnormal end of task (abend) will occur. If step completion code (offset 55) equals 0322 or 0522, IEFUTL caused the abend. If step completion code equals 0722, IEFUSO caused the abend. 7 If zero, then normal completion. If 1, step was flushed.
Device allocation start time, in hundredths of a second.
Problem program start time, in hundredths of a second.
Step CPU time under SRBs, in hundredths of a second. This field includes the CPU time for various supervisory routines that are dispatched via SRBs: locking routines, page resolution, swap control, cross-memory communications (WAIT, POST, I/O POST), and TQE scheduling. CPU time is not expected to be constant between different runs of the same job step. (See Chapter 11, “CPU Time.”)
Record indicator Bit Meaning When Set 0-3 Reserved. 4 Field SMF34_TIVCPUTM is not valid. An overflow condition is when the length of the value for the step CPU time under TCBs is greater than 3 bytes. This condition is not recorded in the type 34 record (TIVCPUTM). The time 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 Device data not recorded. When there are more than 1635 DD statements, device data is not collected for the type 34 record. The data is available in the type 30 record. 6 EXCP count may be wrong. For more information on EXCP count, see Chapter 10, “EXCP Count.” 7 If zero, storage is virtual (if 1, storage is real). 8-15 Reserved.
Offset from the beginning of the record header to relocate section.
Length of execute channel program (EXCP) count fields.
For each device assigned to each non-spooled data set, there is an eight-byte entry with the following format:
Data set access information. Note: Virtual I/O devices are identified by the following: Device Class 0 Unit Type 0 Device Number 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: v IEF237I X'3FFF' ALLOCATED TO ddname v IEF237I X'7FFF' ALLOCATED TO ddnameindicate 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.
Execute channel program (EXCP) count. See offset 102 — SMF34_TIVRIN.
Length of accounting section (excluding this field).
Step CPU time under task control blocks (TCB), in hundredths of a second. This field includes the CPU time for all tasks that are dispatched via TCBs below the level of RCT. CPU time is not expected to be constant between different runs of the same job step. (See Chapter 11, “CPU Time.”)
Number of accounting fields.
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.
Number of non-VIO (virtual input/output) page-ins for this step. This field includes page-ins required through page faults, specific page requests, and page fixes. It does not include page reclaims, page-ins for VIO data sets, and page-ins for the common area.
Number of non-VIO (virtual input/output) page-outs for this step. This field includes page-outs required through specific page requests as well as those pages “stolen” by the paging supervisor through infrequent use. It does not include page-outs for VIO data sets, and page-outs for the common area.
Number of address space swap sequences. A swap sequence consists of a swap-out and swap-in of an address space.
Number of pages swapped in. This field includes: local system queue area (LSQA), fixed pages, and those pages that the real storage manager determined to be active when the address space was swapped out. It does not include page reclaims nor pages found in storage during the swap-in process (such as pages brought in via SRBs started after completion of swap-in Stage 1 processing).
Number of pages swapped out. This field includes: local system queue area (LSQA), private area fixed pages, and private area non-fixed changed pages.
Number of virtual input/output (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.
Number of virtual input/output (VIO) page-outs for this step. This field includes page-outs resulting from specific page requests on a VIO window, as well as those pages “stolen” by the paging supervisor through infrequent use. It does not include VIO swap-outs or page-outs for the common area.
Step service, in service units. This field is calculated as total job service minus the accumulated job service before this step’s initialization.
Step transaction active time, in 1024-microsecond units. Calculated as total job transaction active time minus the accumulated transaction active time before this step’s initialization.
Beginning with z/OS V1R3, this field is always zero.
Step transaction residency time, in 1024-microsecond units. That is the amount of time the transaction was in real storage.
Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted.
Number of virtual input/output (VIO) reclaims for this step.
Number of common area page-ins for this step (link pack area (LPA) + CSA).
Number of hiperspace page-ins from auxiliary to processor storage.
Number of pages “stolen” from the storage for this step.
Number of page seconds for this step, in page millisecond units. Calculated as: the number of pages used by this step times the processing time it held that number of pages.
Number of link pack area (LPA) page-ins for the step.
Number of hiperspace page-outs from processor to auxiliary storage.
Step CPU service, in service units.
Step I/O service, in service units.
Step main storage service, in service units.
Step SRB service, in service units.
Terminal symbolic name.
The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.