Go to Home Page
Questions?
Call 1-800-572-5517
 
  Go to Home Page  
  See all products
  See price schedules
  See manuals, tutorials, articles
  Download a free 30-day trial
  See user testimonials
  About Pacific Systems Group
 
 
SMF Tools
  See SMF Record Layouts
  See Sample SMF Reports
  Learn How to Export SMF Data
  Download Free SMF Reporting Software (30 days)
 
One of the greatest SMF record parsing programming languages I've ever seen. Chief, Large Systems Services Branch, NIH
  Choose Spectrum Writer to add 4GL to your product
  Free 60-Page Book (PDF) - How to Make an SMF Report
Spectrum DCOLLECT Reporter - the 4GL DCOLLECT Report Writer.

Spectrum SMF Writer - the 4GL SMF Report Writer.

SMF Type 34 Record

This table shows the record layout for type 34 SMF records
(TS-Step Termination).

List of other SMF record layouts available.
List of sample SMF reports.

Purpose: Record type 34 is written when the TSO/E logoff function processes a job step termination.

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

This record identifies the job by job name, logon time and date, user identification, program name, and performance group number. If accounting numbers (which can be alphameric) were specified on the EXEC card, they are included. This record contains operating information such as:

  • Initiator start time
  • Number of TPUTs issued
  • Number of TGETs satisfied
  • Termination status
  • Device allocation start time
  • Problem program start time
  • Step CPU time
  • Step service
  • Storage protect key
  • Number of page-ins
  • Number of page-outs
  • Number of swap-ins
  • Number of swap-outs (for both VIO and non-VIO data sets)

Record type 34 has an entry for each non-spooled data set that was defined by a DD statement. Each entry lists the device class, unit type, device number, and execute channel program (EXCP) count for the data set.

Notes:
1. Data sets are recorded in 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.)
2. For data sets that are dynamically unallocated, the data set entry information is in record type 40 — not in record type 34.
3. For more information on EXCP count and CPU time, see Chapter 10, “EXCP Count” and Chapter 11, “CPU Time” respectively.

It's easy to report on SMF 34 data!

SMF Spectrum Writer
We have a low-cost 4GL report writer especially for SMF files. It's called Spectrum SMF Writer.

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.

Plus, Spectrum SMF Writer can export SMF data as comma delimited files to use on your PC.
 
Try It FREE Now!

SMF Type 34 Record -- TS-Step Termination
Offset
(Dec.)
Offset
(Hex)
NameLengthFormatDescription
00SMF34_
TIVRLEN
2binary
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.
22SMF34_
TIVRSEG
2binary
Segment descriptor (see record length field).
44SMF34_
TIVRFLG
1binary
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.
55SMF34_
TIVRCDTY
1binary
Record type 34 (X'22').
66SMF34_
TIVRCDTS
4binary
Time since midnight, in hundredths of a second, that the record is passed to the SMF writer. This is the time the step ended.
10ASMF34_
TIVRCDTE
4packed
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.
14ESMF34_
TIVCPUID
4EBCDIC
System identification (from the SID parameter).
1812SMF34_
TIVUIF
8EBCDIC
Job name.
261ASMF34_
TIVONTME
4binary
Logon time, in hundredths of a second.
301ESMF34_
TIVONDTE
4packed
Logon date, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
3422SMF34_
TIVUDATA
8EBCDIC
User-defined identification field (taken from common exit parameter area, not from USER=parameter on job statement).
422ASMF34_
TIVINVSQ
1binary
Step number (this field always equals 1).
432BSMF34_
TIVSIT
4binary
Time since midnight, in hundredths of a second, that the initiator selected this step.
472FSMF34_
TIVOUTCT
4binary
Number of lines of terminal output, that is, number of TPUTs issued.
5133SMF34_
TIVINCT
4binary
Number of lines of terminal input, that is, number of TGETs satisfied.
5537SMF34_
TIVSTAT
2binary
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).
5739SMF34_
TIVPRI
1binary
Address space dispatching priority (taken from DPTRTY=parameter on the EXEC card or the default APG value).
583ASMF34_
TIVPRGNM
8EBCDIC
Program name (taken from PGM=parameter on EXEC card). If a backward reference was used, then this field contains *.DD.
6642SMF34_
TIVINVNM
8EBCDIC
Step name (taken from name on EXEC card).
744ASMF34_
TIVRSV5
2Reserved.
Note that SMF34TIVEFRGN, formerly a two-byte field at this offset, has been increased to four bytes and moved to offset 82.
764CSMF34_
TIVSYST
2binary
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.
784ESMF34_
TIVMCRE
2binary
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.
8050SMF34_
TIVRVC
2--
Reserved.
8252SMF34_
TIVEFRGN
4binary
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.
8656SMF34_
TIVSPK
1binary
Storage protect key, in the form xxxx0000 where xxxx is the key.
8757SMF34_
TIVSTI
1binary
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.
8858SMF34_
TIVRV1
2--
Reserved.
905ASMF34_
TIVAST
4binary
Device allocation start time, in hundredths of a second.
945ESMF34_
TIVPPST
4binary
Problem program start time, in hundredths of a second.
9862SMF34_
TIVRV2
1--
Reserved.
9963SMF34_
TIVSRBT
3binary
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.”)
10266SMF34_
TIVRIN
2binary
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.
10468SMF34_
TIVRLCT
2binary
Offset from the beginning of the record header to relocate section.
1066ASMF34_
TIVVAR
2binary
Length of execute channel program (EXCP) count fields.
Execute Channel Program (EXCP) Section
For each device assigned to each non-spooled data set, there is an eight-byte entry with the following format:
(Offset from beginning of record: 108)
00SMF34_
TIVEXCP
8Structure
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.
00SMF34_
TIVDEVC
1binary
Device class.
11SMF34_
TIVUTYP
1binary
Unit type.
22SMF34_
TIVCUAD
2binary
Device number.
44SMF34_
TIVNEXCP
4binary
Execute channel program (EXCP) count. See offset 102 — SMF34_TIVRIN.
Accounting Section
(Offset from beginning of record: 108 + SMF34_TIVVAR)
00SMF34_
TIVVARA
1binary
Length of accounting section (excluding this field).
11SMF34_
TIVCPUTM
3binary
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.”)
44SMF34_
TIVNBRAC
1binary
Number of accounting fields.
55SMF34_
TIVACFLD
variableEBCDIC
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.
Relocate Section
(Offset from beginning of record: SMF34_TIVRLCT +4)
00SMF34_
TIVPGIN
4binary
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.
44SMF34_
TIVPGOUT
4binary
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.
88SMF34_
TIVRGNS
4binary
Number of address space swap sequences. A swap sequence consists of a swap-out and swap-in of an address space.
12CSMF34_
TIVSIN
4binary
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).
1610SMF34_
TIVSOUT
4binary
Number of pages swapped out. This field includes: local system queue area (LSQA), private area fixed pages, and private area non-fixed changed pages.
2014SMF34_
TIVVPI
4binary
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.
2418SMF34_
TIVVPO
4binary
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.
281CSMF34_
TIVSST
4binary
Step service, in service units. This field is calculated as total job service minus the accumulated job service before this step’s initialization.
3220SMF34_
TIVACT
4binary
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.
3624SMF34_
TIVPGNO
2binary
Beginning with z/OS V1R3, this field is always zero.
3826SMF34_
TIVTRANT
4binary
Step transaction residency time, in 1024-microsecond units. That is the amount of time the transaction was in real storage.
422ASMF34_
TIVCPM
4binary
Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted.
462ESMF34_
TIVRCLAM
4binary
Number of virtual input/output (VIO) reclaims for this step.
5032SMF34_
TIVCPGIN
4binary
Number of common area page-ins for this step (link pack area (LPA) + CSA).
5436SMF34_
TIVHSPI
4binary
Number of hiperspace page-ins from auxiliary to processor storage.
583ASMF34_
TIVPGSTL
4binary
Number of pages “stolen” from the storage for this step.
623ESMF34_
TIVPGSEC
8binary
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.
7046SMF34_
TIVLPAI
4binary
Number of link pack area (LPA) page-ins for the step.
744ASMF34_
TIVHSPO
4binary
Number of hiperspace page-outs from processor to auxiliary storage.
784ESMF34_
TIVCPUS
4binary
Step CPU service, in service units.
8252SMF34_
TIVIOCS
4binary
Step I/O service, in service units.
8656SMF34_
TIVMSOS
4binary
Step main storage service, in service units.
905ASMF34_
TIVSRBS
4binary
Step SRB service, in service units.
945ESMF34_
TIVTSN
8EBCDIC
Terminal symbolic name.

The table above is based on the description provided by IBM in its "MVS Systems Management Facilities (SMF)" manual.

Copyright 2017.
Pacific Systems Group.
All rights reserved.


Spectrum Writer 4GL - the economical alternative to SAS, Easytrieve, DYL-280...

Home | Products | Prices | Documentation | 30-Day Trials | Customer Reviews | Company | FAQ | Sample Reports | SMF Records
Send Your Comments or Questions