SMF Type 4 Record
This table shows the record layout for type 4 SMF records
It's easy to report on SMF 4 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 4 (X'04').
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.
Date when the record is passed to the SMF writer, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description. This is the date when the step terminated.
System identification (from the SID parameter).
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).
Time since midnight, in hundredths of a second, that the reader recognized the JOB card (for this job).
Date when the reader recognized the JOB card (for this job), 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 (first step=1, etc.).
Time since midnight, in hundredths of a second, that the initiator selected this step.
Date when the initiator selected this step, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
Number of card-image records in DD DATA and DD* data sets read by the reader for the step.
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).
Address space dispatching priority (taken from DPRTY= parameter on EXEC card or the default APG value). For more information see z/OS MVS Initialization and Tuning Guide.
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).
Reserved. SMF4RSH0, 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 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.
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.
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.
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 3 Canceled by exit IEFUSI 4 Canceled by exit IEFACTRT 5 Step is to be restarted 6 If 0, normal completion. If 1, ABEND. If step completion code (offset 55) equals 0322 or 0522, IEFUTL caused ABEND. If step completion code equals 0722, IEFUSO caused ABEND. 7 If 0, 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.
Record indicator Bit Meaning When Set 0-3 Reserved 4 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 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 EXCP count might be wrong. For more information on EXCP count, see Chapter 10, “EXCP Count.” 7 If 0, storage is virtual. If 1, storage is central (real). 8-15 Reserved.
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.
Length of device entry portion of record. Equals: (8 times the number of devices) + 2
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.
EXCP count (see offset 102).
After the device entries are the following fields:
Length of accounting section, excluding this field.
Step CPU time under TCBs, 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. For more information on CPU time, 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, non-swap 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, pages that are swapped in, and page-ins for the common area.
Number of non-VIO, non-swap page-ins for this step. This field includes page-outs required through 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, pages that are swapped out, and page-outs for the common area.
Number of address space swap sequences. (A swap sequence consists of an address space swap-out and swap-in.)
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 via SRBs started after completion of swap-in Stage 1 processing).
Number of pages swapped out. This field includes: LSQA, private area fixed pages, and private area non-fixed changed pages.
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.
Number of 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 equals: total job service minus the accumulated job service before this step’s initialization.
(SMF4TAT) Step transaction active time, in 1024-microsecond units equals: total job transaction active time minus the accumulated transaction active time before this step’s initialization.
Step performance group number (taken from PERFORM= parameter on JOB or EXEC card or the RESET operator command).
Step transaction residency time in 1024-microsecond units. That is the time the transaction was in central storage.
Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted.
Number of VIO reclaims for this step.
Number of common area page-ins for this step (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. Equals: the number of pages used by this step times the processing time it held that number of pages.
Number of link pack area 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.
The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.