








	*SMF Tools*

SMF Type 30 Record

This table shows the record layout for type 30 SMF records
(Common Address Space Work - z/OS 1.10).

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

Purpose: The type 30 SMF record provides accounting information. It consolidates data that is found in record types 4, 5, 20, 34, 35, and 40 (which simplifies accounting by installation-written post processing routines), and it provides additional information. Use record type 30, because the record types that it replaces are generally not being updated with new measurement data.

SMF writes record type 30 when:

A work unit (such as a TSO/E session, APPC/MVS transaction program, OMVS forked or spawned address space, started task, or batch job) starts. This subtype 1 record identifies the work unit but contains no resource data.
An SMF interval ends, if you requested interval accounting. If this is the first interval since the work unit started, then this subtype 2 record contains the total resources used from the start of the work unit until the end of the current interval. With interval synchronization, this span of time is normally shorter than the length of the SMF global recording interval. For global interval recording without interval synchronization, this span of time is the same as the length of the SMF global recording interval. For other intervals, this subtype 2 record contains the total resources used from the end of the previous interval until the end of the current interval. For system address spaces that do not go through full function start, SMF generates a subtype 6 record that contains the total resources used since the start of the address space. Note that the data in the subtype 6 record is cumulative, unlike the subtype 2 record.
A work unit (such as a TSO/E session, APPC/MVS transaction program, OMVS forked or spawned address space, started task, or batch job) completes. If you requested interval accounting, SMF generates a subtype 3 record that contains the total resources used from the end of the previous recording interval until the end of the work unit. This span of time is normally shorter than the length of the specified recording interval. For a job step, SMF generates a subtype 4 record that contains the total resources used from the time when the job step started until the time when the job step completed. If you requested interval recording, then this subtype 4 record generally contains the accumulated totals of the data in the interval subtype 2 and subtype 3 records that were generated for the step. For a job, SMF generates a subtype 5 record that contains the total resources used from the time when the job started until the time when the job completed. This subtype 5 record generally contains the accumulated totals of the data in the step total subtype 4 records that were generated for the job.

The type 30 record contains operation information such as the job and step start and end times, step CPU time, step termination status, number of records in DD DATA and DD * data sets processed by the step and job, device allocation start time, problem program start time, and storage protect key. The record contains the number of page-ins, page-outs, swap-ins, and swap-outs for both virtual input output (VIO) and non-VIO data sets. The record contains information on the number of hiperspace page moves and the movement of pages between expanded storage and central storage. This data can be used in resource planning. Information is added to account for time spent in hiperspace processing on a step or interval basis. The record contains an entry for each data set defined by a DD statement or dynamic allocation. Each entry lists the device class, unit type, device number, the execute channel program (EXCP) count, and device connect time for the data set. The usage data section contains information that can be used to attribute usage of a product to the address space.

The type 30 record can be used with subtype selectivity function.The subtypes are:

1 Job start or start of other work unit
2 Activity since previous interval ended
3 Activity for the last interval before step termination
4 Step total
5 Job termination or termination of other work unit
6 System address space, which did not go through full function start. When you select subtype 6 for record type 30, the following fields may contain zeros or blank: SMF30PGM, SMF30STM, SMF30PSN, SMF30CL8, SMF30UIF, SMF30USR, SMF30JNM.

Information in specific fields may differ for different subtypes. For example, the record identifies the job (and job step) by the:

Job log identification (job name, time and date that the reader recognized the job card for this job).
Step name
Number of the step within the job
User identification
Program name
Performance group number or service class name
JES job number.

If accounting numbers (which can be alphameric) are specified in the JOB or EXEC statements, they are included. For subtype 1 and subtype 5, the accounting numbers are taken from the JOB statement. For all other subtypes, the accounting numbers are taken from the EXEC statement.

Because some of the information necessary to complete a field is not always available when a type 30 record is written, some fields might be empty. For example, the SMF30AST, SMF30PPS, SMF30SIT, and SMF30STD fields are not filled in for a subtype 1 record.

Because system address spaces do not use full function start, the subtype 6 record is incomplete; that is, only certain fields in each section are valid. All unused fields are set to zero or blank.

The subtype 6 records are written only at the expiration of an interval; the values are cumulative and indicate data collected since the initialization of the address space. If a system address space later goes through full function start, data is not reported for the period between the expiration of the previous interval and the time that the address space goes through full function start. The subtype 6 record contains data for the APPC/MVS Cumulative Resource section, but data in the APPC/MVS Resource section is not reported in subtype 6.

The length of record type 30 is variable. The maximum length of the type 30 record is 32,756 bytes. If the volume of data in the type 30 record is such that the length would exceed the maximum length, one or more additional type 30 records are produced. The additional records contain only the header/self-defining, subsystem, identification, and one or more sections that can repeat. An example of a section that can repeat is the execute channel program (EXCP) section.

Notes:

1. Data sets are recorded in the order of the DD statements; they are not identified by name. However, the data definition name (ddname) is included in the record. (An installation-written IEFUJV exit routine can record this order as each statement is validated). For concatenated DD statements, the ddname is the same on each entry, respectively.
2. CPU time is not expected to be constant between different runs of the same job step.
3. If the SMFPRMxx parameter DDCONS(YES) is specified, then duplicate execute channel program (EXCP) entries are consolidated. If DDCONS(NO) is specified, then duplicate EXCP entries are not consolidated. SMFPRMxx parameters are described in z/OS MVS Initialization and Tuning Reference.
4. If a section is not included in the record, the “number of” entry is zero. For example, subtype 1 does not have a completion segment, and SMF30TON is set to zero to indicate this.
5. If the IEFUSI exit changes the size of the private area, a flag is set in SMF30SFL in the paging and storage section.
6. Specifying the DETAIL parameter of the SMFPRMxx parmlib member for STC includes all EXCP sections in subtypes 4 and 5 for the step or job.
7. Specifying the NODETAIL parameter excludes EXCP sections from subtypes 4 and 5 for STC class subsystem jobs, but not for batch or TSO/E subsystems.

When you use the SMF30CPT field in the Accounting section:

Note that a workload may generate different values for SMF30CPT, if some eligible work for the System z® Application Assist Processor (zAAP) or IBM System z9® Integrated Information Processor and IBM System z10™ Integrated Information Processor (zIIP) running on a standard processor. If a repeatable value is more desirable than the possible performance benefits of letting zAAP or zIIP eligible work run on both specialty CPs and standard processors, specify IFAHONORPRIORITY=NO or IIPHONORPRIORITY=NO in the IEAOPTxx parmlib member.

Interval records may show this number to be hundredth (1/100) of a second less than other related SMF30 fields (such as SMF30_TIME_IFA_ON_CP). This difference is due to rounding differentials while calculating delta values, and will not occur for step end or job end.

If SMF30CPT is zero, and you would like to understand how much CPU time was used by the address space or you require more precise values in general, you can calculate the CPU and SRB time in microseconds (1/1000 of a second using the following formulas:

CPU time: (SMF30CSU * 10) / SMF30CPC * SMF30SUS / 16 = CPU time in microseconds
SRB time: (SMF30SRB * 10) / SMF30SRC * SMF30SUS / 16 = SRB time in microseconds

The CPU and SRB times computed from service units include zAAP time and zIIP time in addition to CP time. The time derived from CPU service is comparable to the sum of fields SMF30CPT, SMF30_TIME_ON_IFA and SMF30_TIME_ON_zIIP for work with no enclave activity. If the zAAP or zIIP processors are faster than the CP, zAAP or zIIP time is normalized to the time expected on the slower CP before service units are computed. Therefore, the derived time contains normalized zAAP or zIIP time. Field SMF30ZNF contains the normalization factor used. Enclave time is summed with address space time in SMF30CPT. The computation above includes dependent enclave time but does not include independent enclave time. To compute independent enclave time, substitute SMF30ESU for SMF30CPC in the equation above.

If you use derived processor times, you determine

derived CP time = CPT / (CPT + IFAT + zIIPT) * derived CPU time
derived zIIP time = zIIPT / (CPT + IFAT + zIIPT) * derived CPU time
derived zAAP time = IFAT / (CPT + IFAT + zIIPT) * derived CPU time

where:

CPT = SMF30CPT
IFAT = SMF30_TIME_ON_IFA
zIIPT = SMF30_TIME_ON_ZIIP

assuming the denominator is not zero.

It's easy to report on SMF 30 data! (Jump to sample reports)

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.

SMF Type 30 Record -- Common Address Space Work - z/OS 1.10

Offset
(Dec.)

Offset
(Hex)

Name

Length

Format

Description

SMF30LEN

binary

Record Length. This field along with the next, are referred to as the RDW (record descriptor word).

SMF30SEG

binary

Segment descriptor (see record length field).

SMF30FLG

binary

System indicator:

Bit	Meaning When Set
0	Subsystem identification follows system identification
1	Subtypes used
2	Reserved
3-6	Version indicators
7	Reserved.

SMF30RTY

binary

Record type 30 (X'1E').

SMF30TME

binary

Time since midnight, in hundredths of a second, that the record was moved to the SMF buffer.

SMF30DTE

packed

Date that the record was moved to the SMF buffer, in the form 0cyydddF (in local time).

SMF30SID

EBCDIC

System identification (from the SID parameter).

SMF30WID

EBCDIC

Work type indicator for the address space. The value identifies the type of address space that is being reported on (for example: “STC” for started tasks and system address spaces, “TSO” for TSO/E users, etc).

SMF30STP

binary

Record subtype.

Sub type	Meaning
1	Job start or start of other work unit
2	Activity since previous interval ended
3	Activity for the last interval before step termination
4	Step total
5	Job termination or termination of other work unit
6	System address space, which did not go through full function start. When you select subtype 6 for record type 30, the following fields may contain zeros or blank: SMF30PGM, SMF30STM, SMF30PSN, SMF30CL8, SMF30UIF, SMF30USR, SMF30JNM.

SMF30SOF

binary

Offset to subsystem section from start of record, including the record descriptor word (RDW).

SMF30SLN

binary

Length of subsystem section.

SMF30SON

binary

Number of subsystem sections.

SMF30IOF

binary

Offset to identification section from start of record, including the record descriptor word (RDW).

SMF30ILN

binary

Length of identification section.

SMF30ION

binary

Number of identification sections.

SMF30UOF

binary

Offset to I/O activity section from start of record, including the record descriptor word (RDW).

SMF30ULN

binary

Length of I/O activity section.

SMF30UON

binary

Number of I/O activity sections.

SMF30TOF

binary

Offset to completion section from start of record, including the record descriptor word (RDW).

SMF30TLN

binary

Length of completion section.

SMF30TON

binary

Number of completion sections.

SMF30COF

binary

Offset to processor section from start of record, including the record descriptor word (RDW).

SMF30CLN

binary

Length of processor section.

SMF30CON

binary

Number of processor sections.

SMF30AOF

binary

Offset to accounting section from start of record, including the record descriptor word (RDW).

SMF30ALN

binary

Total length of the single accounting section.

SMF30AON

binary

Number of variable length text segments.

SMF30ROF

binary

Offset to storage section from start of record, including the record descriptor word (RDW).

SMF30RLN

binary

Length of storage section.

SMF30RON

binary

Number of storage sections.

SMF30POF

binary

Offset to performance section from start of record, including the record descriptor word (RDW).

SMF30PLN

binary

Length of the performance section.

SMF30PON

binary

Number of performance sections.

SMF30OOF

binary

Offset to operator section from start of record, including the record descriptor word (RDW).

SMF30OLN

binary

Length of the operator section.

SMF30OON

binary

Number of operator sections.

SMF30EOF

binary

Offset to the execute channel program (EXCP) section from start of record, including the record descriptor word (RDW).

100

SMF30ELN

binary

Length of the execute channel program (EXCP) section, in this record.

102

SMF30EON

binary

Number of execute channel program (EXCP) sections in this record.

104

SMF30EOR

binary

Number of execute channel program (EXCP) sections in subsequent records. When this number exceeds two bytes, it is invalid. See SMF30EOS for the correct value.

106

SMF30RVD

Reserved.

108

SMF30EOS

binary

Number of execute channel program (EXCP) sections in subsequent records.

112

SMF30DRO

binary

Offset to APPC/MVS resource section from start of record, including the record descriptor word (RDW).

116

SMF30DRL

binary

Length of APPC/MVS resource section.

118

SMF30DRN

binary

Number of APPC/MVS resource sections in this record (this number is 0 or 1).

120

SMF30ARO

binary

Offset to APPC/MVS cumulative resource section from start of record, including the record descriptor word (RDW).

124

SMF30ARL

binary

Length of APPC/MVS cumulative resource section.

126

SMF30ARN

binary

Number of APPC/MVS cumulative resource sections in this record (this number is 0 or 1).

128

SMF30OPO

binary

Offset to z/OS UNIX System Services process section.

132

SMF30OPL

binary

Length of z/OS UNIX System Services process section.

134

SMF30OPN

binary

Number of z/OS UNIX System Services process sections on current record.

136

SMF30OPM

binary

Number of z/OS UNIX System Services process sections on subsequent records.

140

SMF30UDO

binary

Offset to first usage data section from the start of the record, including the record descriptor word (RDW).

144

SMF30UDL

binary

Length of each usage data section - ‘76’.

146

SMF30UDN

binary

Number of usage data sections in this record.

148

SMF30UDS

binary

Number of usage data sections in subsequent records.

152

SMF30RMO

binary

Offset to first automatic restart management section.

156

SMF30RML

binary

Length of automatic restart management section.

158

SMF30RMN

binary

Number of automatic restart management sections.

160

SMF30RMS

binary

Number of automatic restart management sections in subsequent records.

164

SMF30MOF

binary

Offset to the Multisystem Enclave Remote Data section.

168

SMF30MLN

binary

Length of MultiSystem Enclave Remote System Data section.

170

SMF30MNO

binary

Number of MultiSystem Enclave Remote System Data sections in this record.

172

SMF30MOS

binary

Number of MultiSystem Enclave Remote System Data sections in subsequent records.

Subsystem Section
This section contains general record and system identification information that you can use to determine the level of information on the rest of the record.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset: SMF30SOF
Length: SMF30SLN
Number: SMF30SON - This field will always be ‘1’ as this section is on each of the Type 30 records that is generated.
(Offset from beginning of record: SMF30SOF)

SMF30TYP

binary

Subtype identification

Value	Meaning
1	Job start or start of other work unit.
2	Activity since previous interval ended. Produced only when interval recording is active.
3	Activity for the last interval before step termination. Produced only when interval recording is active.
4	Step total
5	Job termination or termination of other work unit.
6	System address space.

SMF30RS1

Reserved.

SMF30RVN

EBCDIC

Record version number

Value	Meaning
X’05’	MVS/SP Version 5
X’04’	MVS/SP Version 4
X’03’	MVS/SP Version 3
X’02’	MVS/SP Version 2
X’01’	VS2

SMF30PNM

EBCDIC

Subsystem or product name, for example SMF.

SMF30OSL

EBCDIC

MVS software level (consists of an acronym and the version, release, and modification level numbers).

SMF30SYN

EBCDIC

System name (from the SYSNAME parameter in the IEASYSxx parmlib member).

SMF30SYP

EBCDIC

Sysplex name (from the SYSPLEX parameter in the COUPLExx parmlib member).

Identification Section
This section contains general address space and user information which can be used to identify the address space that the data is being reported for or to merge this record with other records that are generated for this address space.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30IOF
Length SMF30ILN
Number SMF30ION - This field will always be ‘1’ as this section is on each of the Type 30 records that are generated.
(Offset from beginning of record: SMF30IOF)

SMF30JBN

EBCDIC

Job or session name. The job name, time and date that the reader recognized the JOB card (for this job) constitute the job log identification.

SMF30PGM

EBCDIC

Program name (taken from PGM= parameter on EXEC card). If a backward reference was used, this field contains PGM=*.DD.

SMF30STM

EBCDIC

Step name (taken from name on EXEC card).

SMF30UIF

EBCDIC

User-defined identification field (taken from common exit parameter area, not from USER=parameter on job statement).

SMF30JNM

EBCDIC

JES job identifier. Jobs scheduled by the APPC/MVS transaction scheduler (ASCH) start with an “A” followed by a seven-digit number.

SMF30STN

binary

Step number (first step = 1, etc.).

SMF30CLS

binary

Job class (blank for TSO/E session or started tasks).

Reserved.

SMF30PGN

binary

Beginning with z/OS V1R3, this field is always zero.

SMF30JPT

binary

JES input priority. If no value is specified for the PRTY parameter (on the JOB card), this field contains: v For JES3, the default priority specified on the JES3 STANDARDS initialization card v For JES2, a zero.Note that JES2 does not use the priority value reported in the field. (The JES2 job selection priority is requested via the JES2 PRIORITY control statement.)

SMF30AST

binary

Device allocation start time, in hundredths of a second.

SMF30PPS

binary

Problem program start time, in hundredths of a second.

SMF30SIT

binary

Time since midnight, in hundredths of a second, that the initiator selected this step or job.

SMF30STD

packed

Date that the initiator selected this step, in the form 0cyydddF.

SMF30RST

binary

Time since midnight, in hundredths of a second, that the reader recognized the JOB card (for this job).

SMF30RSD

packed

Date that the reader recognized the JOB card (for this job), in the form 0cyydddF.

SMF30RET

binary

Time since midnight, in hundredths of a second, that the reader recognized the end of the job or started task (reader stop time). For TSO/E this is the logon enqueue time.

SMF30RED

packed

Date that the reader recognized the end of the batch job or started task (reader stop date), in the form 0cyydddF.

SMF30USR

EBCDIC

Programmer’s name.

100

SMF30GRP

EBCDIC

RACF group ID. 0 = RACF is not active.

108

SMF30RUD

EBCDIC

RACF user ID. 0 = RACF is not active.

116

SMF30TID

EBCDIC

RACF terminal ID. This field is zero if RACF is not active (or the user is not a terminal user).

124

SMF30TSN

EBCDIC

Terminal symbolic name.

132

SMF30PSN

EBCDIC

The name of the step that invoked the procedure. This field contains blanks if not part of a procedure.

140

SMF30CL8

EBCDIC

8-character job class (left justified, padded with blanks). For JES2, taken from the SMF30CLS field (if not specified), blank for TSO session or started tasks. For JES3, taken from CLASS= parameter on //* MAIN card (if valid), or the default (JES3BATCH).

148

SMF30ISS

binary

Time and date that the interval started for subtype 2 and 3 records, in time-of-day (TOD) format, an unsigned 64-bit fixed-point number where bit 51 is equivalent to 1 microsecond. The representation of this value in local time is stored in SMF30IST and SMF30IDT. Variations in setting the local time can make the times appear to be out of synchronization.

156

SMF30IET

binary

Time and date that the interval ended for subtype 2 and 3 records, in time-of-day (TOD) format, an unsigned 64-bit fixed-point number where bit 51 is equivalent to 1 microsecond. If you requested synchronized interval recording, you can use this field to compare this record with other records generated at the end of the same interval. If the address space being reported was not swapped in when the interval ended then the time contained in this field might be earlier than the time that the record was generated.

164

SMF30SSN

binary

Substep number. This field is set to zero for non-OpenMVS steps. When the OpenMVS exec function is requested, a new substep is begun and this value is incremented.

168

SMF30EXN

binary

Program name. For an OpenEdition program, this contains the name, for up to 16 bytes, starting after the last slash in the filename, of the program that was run. The OpenEdition name ends with the null character X'00'. For an MVS program, it is an unqualified name of up to 8 characters of the program that was executed. The MVS program name is padded with blanks to a length of 16 characters. For example, for an OpenEdition name of /usr/joe/somepgm, the field in SMF record type 30 is somepgm ended by X'00'. For an OpenEdition name of /usr/joe/someverylongprogramname, the field is truncated to someverylongprog.

I/O Activity Section
This section contains the summary I/O information at the address space level. This differs from the I/O information in the EXCP sections of the record which present the data at a DD Name/Device level.
Note: The system adjusts the connect time for FICON DASD to be 1 millisecond per request. This value differs from the channel reported connect time.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30UOF
Length SMF30ULN
Number SMF30UON - Reports the number of I/O activity sections on the current record. Because only one I/O activity section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30UOF)

SMF30INP

binary

Number of card-image records in DD DATA and DD* data sets read by the reader for the map. This field is not set for subtypes 2 or 3. Offsets Name Length Format Description

SMF30TEP

binary

Total blocks transferred (accumulated execute channel program (EXCP) counts).

SMF30TPT

binary

Number of TPUTS (terminal writes) for a TSO/E session. If a batch job or a started task successfully processes TPUTs, this field might be non-zero for batch jobs or started tasks.

SMF30TGT

binary

Number of TGETS (terminal reads) for a TSO/E session.

SMF30RDR

binary

Reader device class as defined in JESPARMS. 0 — for TSO/E sessions or started tasks.

SMF30RDT

binary

Reader device type as defined in JESPARMS. 0 — for TSO/E sessions or started tasks.

SMF30TCN

binary

Total device connect time (in 128 micro-second units) for this address space. For a DIV object, this field contains total device connect time for reads, writes, and re-reads.

SMF30DCF

binary

Flag word

Bit	Meaning
0	Device connect time may be incorrect If this flag is set, the system resources manager (SRM) disabled the channel measurement while the job was running. If channel measurement is disabled, device connect time is not recorded. Thus, if this bit is set, SMF30TCN and SMF30DCT reflect less than the actual total connect time.
1	If this bit is on, the following fields contain incomplete data: (SRM could not deliver deltas or values for this interval): SMF30AIC SMF30EIC SMF30AID SMF30EID SMF30AIW SMF30EIW SMF30AIS SMF30EIS
2	Field SMF30TEP is invalid
3-31	Reserved.

SMF30RSB

Reserved.

SMF30TRR

binary

Total address space REREAD count.

SMF30AIC

binary

DASD I/O connect time, in 128-microsecond units, for address space plus dependent enclaves.

SMF30AID

binary

DASD I/O disconnect time, in 128-microsecond units, for address space plus dependent enclaves.

SMF30AIW

binary

DASD I/O pending plus control unit queue time, in 128-microsecond units, for address space plus dependent enclaves.

SMF30AIS

binary

DASD I/O start subchannel count for address space plus dependent enclaves.

SMF30EIC

binary

DASD I/O connect time, in 128-microsecond units, for indpendent enclaves owned by the address space.

SMF30EID

binary

DASD I/O disconnect time, in 128-microsecond units, for independent enclaves owned by the address space.

SMF30EIW

binary

DASD I/O pending plus control unit queue time, in 128-microsecond units, for independent enclaves owned by the address space.

SMF30EIS

binary

DASD I/O start subchannel count for independent enclaves.

SMF30TEX

binary

Total blocks transferred - accumulated EXCP counts. This field is the 8-byte equivalent of SMF30TEP, but this field remains valid after SMF30TEP is invalid

Completion Section
This section contains the completion information for the step on the Step Termination record (Subtype-4) and for the job on the Job Termination record (Subtype-5). This section does not appear on the Job Initialization (Subtype-1) or Interval (Subtype-2 and 3) records.
Note: The SMF30STI field also contains some general record indicator flags which are not necessarily completion in nature. The system may fail a step or job even if the return code is zero. This could happen, for example, as a result of specifying CATLG_ERR FAILJOB(YES) and incurring that type of post execution error. (A return code is generated by the application program and is never changed by the operating system.) A user can deduce that a step failed due to a “post execution error” if bit SMF30SYE in the two-byte SMF30STI field in the SMF30 subtype 4 record is on.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30TOF
Length SMF30TLN
Number SMF30TON - Reports the number of completion sections on the current record. Because only one completion section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30TOF)

SMF30SCC

binary

Step completion code:
X'0ccc'	indicates system abnormal end of task (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 0.

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 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.

Use this field in conjunction with the job/step termination indicator field, SMF30STI.

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 step termination record (subtype 4). In this case, the field, SMF30SCC, can contain X'nnnn' or X'0000'. If an abend occurred in the job, the job termination indicator (bit 7 in the SMF30STI field).

SMF30STI

binary

Step/Job 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 zero, then normal completion. If 1, then abnormal end of task (abend). If step completion code equals 0322 or 0522, then IEFUTL caused the abend. If step completion code equals 0722, then IEFUSO caused the abend.
7	If zero, then normal completion. If 1, then step was flushed.
8	EXCP counts might be incorrect because the record did not include all the DD statements.
9	Previous interval record was not written because an error occurred. The cumulative count might be incorrect because the counters were cleared.
10	EXCP sections were not merged from the interval to the step record or from the step to the job record
11	Step completed with a “post execution” error. Post-execution errors include a failure that occurred because the ALLOCxx parmlib member specified CATLG_ERR FAILJOB(YES).
12	Step completed due to OpenMVS exec function request.
13	JOB abnormally ended because of COND= condition on the JOB card. This flag will be set on in the subtype 5 job termination record only.
14-15	Reserved.

SMF30ARC

binary

Abend reason code.

Processor Accounting Section
Processor Accounting Section This section contains various Processor times for the address space for the period that the record represents.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30COF
Length SMF30CLN
Number SMF30CON - Reports the number of processor accounting sections on the current record. Because only one processor accounting section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30COF)

SMF30PTY

binary

Reserved.

SMF30TFL

binary

Invalid timer flags

Bit	Meaning When Set
0	Indicates that timer flags are used.
1	SMF30CPT has an invalid value due to a timer value calculation error.
2	SMF30CPS has an invalid value due to a timer value calculation error.
3	SMF30JVU has an invalid value due to a timer value calculation error.
4	SMF30JVA has an invalid value due to a timer value calculation error.
5	SMF30ISB has an invalid value due to a timer value calculation error.
6	SMF30ICU has an invalid value due to a timer value calculation error.
7	SMF30IVU has an invalid value due to a timer value calculation error.
8	SMF30IVA has an invalid value due to a timer value calculation error.
9	SMF30IIP has an invalid value due to a timer value calculation error.
10	SMF30HPT has an invalid value due to a timer value calculation error.
11	SMF30RCT has an invalid value due to a timer value calculation error.
12	SMF30ASR has an invalid value due to a timer value calculation error.
13	SMF30ENC has an invalid value due to a timer value calculation error.
14	SMF30DET has an invalid value due to a timer value calculation error.
15	Reserved.

SMF30CPT

binary

All standard CPU step time in hundredths of a second. Includes enclave time, preemptable class SRB time, client SRB time. Also includes time consumed by IFA eligible work running on a standard processor. For time spent on an IFA, see SMF30_TIME_ON_IFA.

Because the times used the CPU and SRB time in microseconds (1/100 of a second using the following formulas:
CPU time: (SMF30CSU * 10) / SMF30CPC * SMF30SUS / 16 = CPU time in microseconds
SRB time: (SMF30SRB * 10) / SMF30SRC * SMF30SUS / 16 = SRB time in microseconds

Note that a workload may generate different values for SMF30CPT if some IFA eligible work runs on a standard processor. If a repeatable value is more desirable than the possible performance benefits of letting IFA eligible work run on both IFAs and standard processors, specify IFAHONORPRIORITY=NO in the IEAOPTxx parmlib member.

Interval records may show this number to be hundredth (1/100) of a second less than other related SMF30 fields (such as SMF30_TIME_IFA_ON_CP). This diffeence is due to rounding differentials while calculating delta values, and will not occur for step end and/or job end.

This value includes the value in field SMF30OST.

SMF30CPS

binary

Step CPU time under the service request block (SRB), in hundredths of a second.

You can calculate the SRB time in microseconds (1/100 of a second using the following formula:
(SMF30SRB * 10) / SMF30SRC * SMF30SUS / 16 = SRB time in microseconds

This value includes the value in field SMF30OST.

SMF30ICU

binary

Initiator CPU time under the task control block (TCB), in hundredths of a second. This field is set at step termination.

SMF30ISB

binary

Initiator CPU time under the service request block (SRB), in hundredths of a second. This field is set at step termination.

SMF30JVU

binary

Step vector CPU time, in hundredths of a second.

SMF30IVU

binary

Initiator vector CPU time, in hundredths of a second. This field is set at step termination.

SMF30JVA

binary

Step vector affinity time, in hundredths of a second.

SMF30IVA

binary

Initiator vector affinity time, in hundredths of a second. This field is set at step termination.

SMF30IST

binary

Interval start time for type 30 subtype 2 and 3 records, in hundredths of a second.

SMF30IDT

packed

Interval start date for type 30 subtype 2 and 3 records, in the form 0cyydddF.

SMF30IIP

binary

Amount of CPU time used to process I/O interrupts, in hundredths of a second.

SMF30RCT

binary

Amount of CPU time used by the region control task (RCT), in hundredths of a second.

SMF30HPT

binary

CPU time consumed for the step, in hundredths of a second, to support requests for data to be transferred between a hiperspace and an address space, when the hiperspace is backed by expanded storage. The CPU time may vary depending on the availability of expanded storage.

SMF30CSC

binary

Integrated Cryptographic Service Facility/MVS (ICSF/MVS) service count. This is the number of cryptographic instructions executed on behalf of caller (within caller’s address space).

SMF30DMI

binary

ADMF-Number of pages moved with ADMF WRITE operation.

SMF30DMO

binary

ADMF-Number of pages moved with ADMF READ operation.

SMF30ASR

binary

Additional CPU time accumulated by the preemptable SRBs and client SRBs for this job, in hundredths of a second. This value is also included in the value in SMF30CPT.

SMF30ENC

binary

CPU time used by the independent enclave, but only when in the WLM enclave. Note that independent enclave time on an IFA is not included. See field SMF30_ENCLAVE_TIME_ON_IFA for that value. SMF30ENC is also part of the value in SMF30CPT.

SMF30DET

binary

CPU time used by the dependent enclave, but only when in the WLM enclave. Note that dependent enclave time on an IFA is not included - see field SMF30_DEP_ENCLAVE_TIME_ON_IFA for that value. SMF30DET is also part of the value in SMF30CPT.

SMF30CEP

binary

Cumulative CPU time consumed for an address space or job while enqueue promoted (in 1.024 millisecond units).

SMF30TF2

binary

Additional timer flags

Bit	Meaning When Set
0	SMF30_TIME_ON_IFA_F has an invalid value due to a timer value calculation error.
1	SMF30_ENCLAVE_TIME_ON_IFA_F has an invalid value due to a timer value calculation error.
2	SMF30_DEP_ENCLAVE_TIME_ON_IFA_F has an invalid value due to a timer value calculation error.
3	SMF30_TIME_IFA_ON_CP_F has an invalid value due to a timer value calculation error.
4	SMF30_ENCLAVE_TIME_IFA_ON_CP_F has an invalid value due to a timer value calculation error.
5	SMF30_DEP_ENCLAVE_TIME_IFA_ON_CP_F has an invalid value due to a timer value calculation error.
6	SMF30_CEPI_F indicates failure in SMF30CEPI.

85 55 SF30T32 1 binary Additional failure flags.

Bit	Meaning When Set
0	SMF30_TIME_ON_zIIP_F SMF30_TIME_ON_SUP_F
1	SMF30_ENCLAVE_TIME_ON_zIIP_F SMF30_ENCLAVE_TIME_ON_SUP_F
2	SMF30_DEP_ENCLAVE_TIME_ON_zIIP_F SMF30_DEP_ENCLAVE_TIME_ON_SUP_F
3	SMF30_TIME_zIIP_ON_CP_F SMF30_TIME_SUP_ON_CP_F
4	SMF30_ENCLAVE_TIME_zIIP_ON_CP_F SMF30_ENCLAVE_TIME_SUP_ON_CP_F
5	SMF30_DEPENC_TIME_zIIP_ON_CP_F SMF30_DEPENC_TIME_SUP_ON_CP_F

SMF30T33

binary

Additional failure flags.

Bit	Meaning When Set
6	SMF30_ENCLAVE_TIME_zIIP_QUAL_F SMF30_ENCLAVE_TIME_SUP_QUAL_F
7	SMF30_DEPENC_TIME_zIIP_QUAL_F SMF30_DEPENC_TIME_SUP_QUAL_F

binary

Reserved.

SMF30_
TIME_
ON_
IFA

binary

CPU time spent on IFA in hundredths of a second (including enclave time).

SMF30_
ENCLAVE_
TIME_
ON_
IFA

binary

Enclave time spent on IFA in hundredths of a second.

SMF30_
DEP_
ENCLAVE_
TIME_
ON_
IFA

binary

Dependent enclave time spent on IFA in hundredths of a second.

100

SMF30_
TIME_
IFA_
ON_
CP

binary

CPU time spent running IFA eligible work on a standard CP in hundredths of a second (including enclave time).

104

SMF30_
ENCLAVE_
TIME_
IFA_
ON_
CP

binary

IFA Enclave time spent on a standard CP in hundredths of a second.

108

SMF30_
DEP_
ENCLAVE_
TIME_
IFA_
ON_
CP

binary

IFA Dependent enclave time spent on a standard CP in hundredths of a second.

112

SMF30CEPI

binary

CPU time consumed for an address space or job while enqueue promoted (in 1.024 millisecond units). Contains only the time consumed during the interval (not cumulative).

116

SMF30_
TIME_
ON_
zIIP

binary

Time spent on zIIP in hundredths of a second (including enclave time).

120

SMF30_
ENCLAVE_
TIME_
ON_
zIIP

binary

Enclave time spent on zIIP in hundredths of a second.

124

SMF30_
DEPENC_
TIME_
ON_
zIIP

binary

Dependent enclave time spent on zIIP in hundredths of a second.

128

SMF30_
TIME_
zIIP_
ON_
CP

binary

CPU time spent on CP in hundredths of a second (including enclave time).

132

SMF30_
ENCLAVE_
TIME_
zIIP_
ON_
CP

binary

zIIP enclave time spent on CP in hundredths of a second.

136

SMF30_
DEPENC_
TIME_
zIIP_
ON_
CP

binary

zIIP dependent enclave time spent on CP in hundredths of a second.

140

SMF30_
ENCLAVE_
TIME_
zIIP_
QUAL

binary

Normalized enclave time spent on zIIP in hundredths of a second.

144

SMF30_
DEPENC_
TIME_
zIIP_
QUALS

binary

Normalized dependent enclave time spent on zIIP in hundredths of a second.

148

SMF30CRP

binary

CPU time consumed for an address space or job while promoted because of chronic resource contention (in 1.024 millisecond units). For interval records, this field contains only the time consumed during the interval itself

Execute Channel Program (EXCP) Section
This section contains the I/O information for a specific DD Name/Device address pair for the address space. There can be multiple EXCP sections for a given address space.
With the SMFPRMxx parameter EMPTYEXCPSEC(NOSUPPRESS) specified, the system generates one EXCP section for each SMS candidate volume. The SMS candidate volume EXCP section contains only the DD name, SMF30DDN. All other fields in the EXCP section are zeros. This is the default behavior.
With SMFPRMxx parameter EMPTYEXCPSEC(SUPPRESS) specified, no empty EXCP sections are created for non-allocated candidate volume in the SMS storage group.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30EOF
Length SMF30ELN
Number SMF30EON - Reports the number of EXCP sections on the current record.

This section also has additional control fields in the ‘header/self-defining’ section:

SMF30EOS reports the number of EXCP sections for the current period on Subsequent Type 30 records. These are known as the ‘chained’ Type 30 records.
SMF30EOR also reports this same information but is only a 2 byte field which can overflow so SMF30EOS is the preferred field for processing this data.

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:
IEF237I X'3FFF' ALLOCATED TO ddname
EF237I 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.
(Offset from beginning of record: SMF30EOF)

SMF30DEV

binary

Device class.

SMF30UTP

binary

Unit type.

SMF30CUA

binary

Device number.

SMF30DDN

EBCDIC

DD Name used to access the data set. Data sets are recorded in the order of the DD statements; they are not identified by dsname. (An installation-written IEFUJV exit routine can record this order as each statement is validated). For concatenated DD statements, the ddname is the same on each entry, respectively.

SMF30BLK

binary

Count of blocks issued for the device against the data set. This field has a maximum value of X'FFFFFFFF' = 4,294,967,295. If it exceeds that value it will wrap to zero and then continue to increase again for additional blocks transferred.

SMF30BSZ

binary

Largest blocksize of the data set

Bit	Meaning When Set
0	Indicated changed blocksize for the data set. Post processors should use this field to avoid the possibility of negative numbers.
0	1-15 Largest blocksize of the data set.

SMF30DCT

binary

Device connect time for this data set (in 128 micro-second units). For DIV object, device connect time is not collected by SMF; however, this field may not always be zero. For example, if a user is using a DIV data set and calls a VSAM utility to process it using the same DD statement, this will result in device connect time being charged by VSAM to the DIV object.

SMF30XBS

binary

Block size value.

Accounting Section
This section contains the user accounting information for the address space and the unit of work that is being reported on. The JOB level accounting information, taken from the ACCT parm of the JOB card is presented on the Job records for the address space (Subtype-1 and Subtype-5); while STEP level accounting information, taken from the ACCT parm of the EXEC card is presented on the Step records for the address space (Subtype-2, Subtype-3 and Subtype-4).
The format of the data in the section is continuous ‘internal text’ which is:

Length: 1 Byte; ‘0’ indicates no associated accounting field
Field Variable - length defined by previous ‘length’ field

Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30AOF
Length SMF30ALN
Number SMF30AON - This field will contain the number of ‘subsections’ in the accounting section (which each subfield is defined above).
(Offset from beginning of record: SMF30AOF)

SMF30ACL

binary

Length of accounting section (excluding this field).

SMF30ACT

variable

EBCDIC

Job or step accounting field.

Storage and Paging Section
This section contains the statistics on the use of different kinds of storage by the address space and the different kinds of paging activity for the address space.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30ROF
Length SMF30RLN
Number SMF30RON - Reports the number of storage and paging sections on the current record. Because only one storage and paging section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30ROF)

SMF30RSV

Reserved.

Note that SMF30RGN, formerly a two-byte field at this offset, has been increased to four bytes and moved to the end of the Storage and Paging Section.

SMF30SFL

binary

Storage Flags. If storage was not allocated (job step was flushed), these fields equal zero.

Bit	Meaning When Set
0	V=R is specified. This bit has no meaning for subtype 5 records.
1	IEFUSI changed region limit values for the extended private area
2	IEFUSI changed memlimit value.
3-7	Reserved.

SMF30SPK

binary

Storage protect key, in the form xxxx0000 where xxxx is the key.

SMF30PRV

binary

Largest amount of storage used from bottom of private area, in 1 K 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 real storage that was used.

SMF30SYS

binary

Largest amount of storage used from top of private area, in 1K units. This storage area includes the local system queue area (LSQA) and the 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 real storage reserved for the program.

SMF30PGI

binary

Number of pages that were paged in from auxiliary storage.

SMF30PGO

binary

Number of pages that were paged out to auxiliary storage.

SMF30CPM

binary

Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted.

SMF30NSW

binary

Number of address space swap sequences. (A swap sequence consists of an address space swap-out and swap-in. Logical swap-out and swap-in are not included.)

SMF30PSI

binary

Number of pages swapped in from auxiliary storage to central storage. This field includes: (local system queue area (LSQA), fixed pages, and pages that the real storage manager determined to be active when the address space was swapping in. It does not include page reclaims or pages found in storage during the swap-in process (such as pages brought in by the service request blocks (SRB), started after completion of swap-in Stage 1 processing).

SMF30PSO

binary

Number of pages swapped out from central storage to auxiliary storage. This field includes: local system queue area (LSQA), private area fixed pages, and private area non-fixed changed pages.

SMF30VPI

binary

Number of VIO page-ins from auxiliary storage to central storage 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.

SMF30VPO

binary

Number of VIO page-outs from central storage to auxiliary storage 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.

SMF30VPR

binary

Number of VIO reclaims.

SMF30CPI

binary

Number of common area page-ins (LPA + CSA) from auxiliary storage to central storage.

SMF30HPI

binary

Number of hiperspace page-ins from auxiliary to processor storage.

SMF30LPI

binary

Number of LPA page-ins from auxiliary storage to central storage.

SMF30HPO

binary

Number of hiperspace page-outs from processor to auxiliary storage.

SMF30PST

binary

Number of pages stolen from this address space.

SMF30PSC

binary

Number of CPU page seconds for this address space, in page millisecond units. (A page millisecond unit equals 1.024 milliseconds.)

SMF30RGB

binary

Private area size in bytes (less than 16 megabytes).

SMF30ERG

binary

Private area size in bytes (greater than 16 megabytes).

SMF30ARB

binary

Maximum virtual storage in bytes allocated from the local system queue area (LSQA) and the SWA subpools (less than 16 megabytes).

SMF30EAR

binary

Maximum virtual storage in bytes allocated from the local system queue area (LSQA) and the SWA subpools (greater than 16 megabytes).

SMF30URB

binary

Maximum virtual storage in bytes allocated from the user subpools (less than 16 megabytes).

SMF30EUR

binary

Maximum virtual storage in bytes allocated from the user subpools (greater than 16 megabytes).

SMF30RGN

binary

Region size established, in 1K units, rounded up to a 4K boundary. The contents of this field is determined as follows:
If the ADDRSPC=REAL parameter is specified in the JCL, the contents of this field equals the amount of contiguous central storage reserved for the program.
If the REGION= parameter value in the JCL exceeds 16 megabytes:
– If the IEFUSI exit changes the region limit or size above 16 megabytes, the contents of this field equals the changed region limit or size
– Otherwise, the contents of this field equals the REGION parameter value (minimum value of 32 megabytes).
If the REGION= parameter value in the JCL equals or is less than 16 megabytes:
– If the IEFUSI exit changes the region limit or size below 16 megabytes, the contents of this field equals the changed region limit or size
– Otherwise, the contents of this field equals the REGION parameter value.

Note: If both the region limit and size are changed, but do not match, the contents of this field equals the smaller of the changed region limit or size.

100

SMF30DSV

binary

Amount of user key data space and hiperspace virtual storage (high water mark) used during the step/job (in megabytes).

104

SMF30PIE

binary

Number of unblocked pages that were paged in from expanded storage.

108

SMF30POE

binary

Number of unblocked pages that were paged out to expanded storage.

112

SMF30BIA

binary

Number of blocked pages that were paged in from auxiliary storage.

116

SMF30BOA

binary

Number of blocked pages that were paged out to auxiliary storage. that were paged out to expanded storage.

128

SMF30KIA

binary

Number of blocks that were paged in from auxiliary storage.

132

SMF30KOA

binary

Number of blocks that were paged out to auxiliary storage.

136

SMF30KIE

binary

Number of blocks that were paged in from expanded storage.

140

SMF30KOE

binary

Number of blocks that were paged out to expanded storage.

144

SMF30PSF

binary

Number of CPU page seconds for the IARVSERV shared central storage frames in use by this address space, in page milliseconds.

152

SMF30PAI

binary

Number of IARVSERV shared pages that were paged in from auxiliary storage in this address space.

156

SMF30PEI

binary

Number of IARVSERV shared pages that were paged in from expanded storage in this address space.

160

SMF30ERS

binary

Expanded storage page residency time in page-milliseconds.

168

SMF30MEM

binary

Memlimit value (in MB).

176

SMF30MES

binary

Source of Memlimit, which is one of the following:

Value	Meaning
X'01'	MEMLIMIT set by SMF.
X'02'	MEMLIMIT set explicitly in the JCL with MEMLIMIT parameter on JOB or EXEC statement.
X'03'	MEMLIMIT is unlimited based on REGION=0 specification.
X'04'	MEMLIMIT set by IEFUSI (even if IEFUSI did not change the value).
X'0A'	System provided a default for MEMLIMIT based on REGION=0 specification and a subsequent curtailment of REGION in the IEFUSI exit.

177

binary

Reserved.

184

SMF30HVR

binary

High water mark for the number of real storage frames that is used to back 64-bit private storage.

192

SMF30HVA

binary

High water mark for the number of auxiliary storage slots that is used to back 64-bit private storage.

200

SMF30HVO

binary

Amount of 64-bit private storage in bytes that is obtained by this step or job. This includes guarded virtual storage.

208

SMF30HVH

binary

High water mark for the number of usable bytes of 64-bit private storage that is obtained by this step or job. This does not include guarded virtual storage.

216

SMF30HSO

binary

Amount of 64-bit shared storage in bytes, which this step or job has addressability or access to.

224

SMF30HSH

binary

High water mark for the number of usable bytes of 64-bit shared storage, which this step or job has access to.

Performance Section
This section contains the SRM service units used by the address space for the period being reported on. For more information on SRM service units, see z/OS MVS Initialization and Tuning Guide.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30POF
Length SMF30PLN
Number SMF30PON - Reports the number of performance sections on the current record. Because only one performance section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30POF)

SMF30SRV

binary

Total service units.

SMF30CSU

binary

CPU service units.

SMF30SRB

binary

Service request block (SRB) service units.

SMF30IO

binary

I/O service units.

SMF30MSO

binary

Main storage occupancy (MSO) service units.

SMF30TAT

binary

System resources manager (SRM) transaction active time, in 1024-microsecond units.

SMF30SUS

binary

Copy of RmctAdjC when this SMF record was produced, number of sixteenths of one CPU microsecond per CPU service unit.

SMF30RES

binary

System resources manager (SRM) transaction residency time, in 1024-microsecond units. That is the amount of time the SRM transaction was in real storage.

SMF30TRS

binary

Number of system resources manager (SRM) transactions.

SMF30WLM

EBCDIC

Workload name. This field is blank (X‘40’) when in workload management compatibility mode.

SMF30SCN

EBCDIC

Service class name. This field will contain SYSOTHER during the time of a WLM POLICY switch.

SMF30GRN

EBCDIC

Resource group name.

SMF30RCN

EBCDIC

Report class name. This field is blank (X‘40’) during the time of a WLM POLICY switch.

SMF30ETA

binary

Independent enclave transaction active time in 1024-microsecond units.

SMF30ESU

binary

IIndependent enclave CPU service units.

SMF30ETC

binary

Independent enclave transaction count.

SMF30PFL

EBCDIC

Scheduling environment name. Binary zeros if no scheduling environment is specified.

SMF30JQT

binary

Job preparation time. This is the elapsed time before the job was first queued for execution. It excludes time to read the job into the system. It includes delays incurred waiting for and during conversion, such as when eligible systems are not active to convert the job. If the JOB statement specified TYPRUN=JCLHOLD, this time is 0. The time is in 1024-microsecond units.

100

SMF30RQT

binary

Time following job preparation when the job was ineligible for execution due to either the job’s eligible systems being inactive or the job’s scheduling environment not being available. The time is in 1024-microsecond units.

104

SMF30HQT

binary

Time following job preparation when the job was ineligible for execution for reasons not included in SMF30RQT. This includes job hold, job class hold, job queue hold, duplicate jobname serialization, and job class execution limits. If the JOB statement specified TYPRUN=HOLD, the time that the job is held for this reason is not included. The time is in 1024-microsecond units.

108

SMF30SQT

binary

Time the job was eligible for execution. This is the amount of time the job waited for an initiator. The time is in 1024-microsecond units. ForJES3, this field includes time the job was ineligible for execution.

112

SMF30PF1

EBCDIC

Performance section flag byte:

X’80’ (SMF30PFJ)	Job service class association was modified by a system operator prior to job initiation.
X’40’ (SMF30PFR)	Job service class association was modified by a system operator during job execution.
X’20’ (SMF30PFF)	Job initiation forced by a system operator.
X’10’ (SMF30RTR)	Job has been restarted. There is one set of SMF30 records for each time the job is restarted.
X’08’ (SMF30MSI)	Remote system data is incomplete.
X’04’ (SMF30WMI)	Job is executing in a workload manager batch initiator.
X’02’ (SMF30CCP)	Service class assigned to the address space was designated CPU-critical in the WLM service definition.
X’01’ (SMF30CSP)	Service class assigned to the address space was designated storage-critical in the WLM service definition

113

SMF30PF2

EBCDIC

Performance section flag byte:

X’80’ (SMF30ASP)	Address space was designated storage-critical.
X’40’ (SMF30SME)	Address space cannot be managed to transaction goals, because “manage region to goals of region” was specified in the WLM service definition.
X’20’ (SMF30CPR)	Address space is currently CPU-protected.
X’10’ (SMF30SPR)	Address space is currently storage-protected.
X’08’ (SMF30PIN)	If this bit is on, the following fields contain incomplete data: (SRM could not deliver deltas or values for this interval) SMF30CSU SMF30MSO SMF30SPR SMF30ESU SMF30PFL SMF30SQT SMF30ETA SMF30PFR SMF30SRB SMF30ETC SMF30RCN SMF30SRV SMF30GRN SMF30RES SMF30SUS SMF30HQT SMF30RQT SMF30TAT SMF30IO SMF30RTR SMF30TRS SMF30JPN SMF30SCN SMF30WLM SMF30JQT SMF30SME

114

SMF30RS4

EBCDIC

Reserved.

115

SMF30ZEP

EBCDIC

Contains information associated with a potential future function, no further details are available at this time.

116

SMF30JPN

EBCDIC

Subsystem collection name from IWMCLSFY SUBCOLN.

124

SMF30MSC

binary

MSO Service Definition Coefficient (SDC) scaled by 10000.

128

SMF30CPC

binary

CPU Service Definition Coefficient (SDC) scaled by 10.

130

SMF30LOC

binary

IOC Service Definition Coefficient (SDC) scaled by 10.

132

SMF30SRC

binary

SRB Service Definition Coefficient (SDC) scaled by 10.

134

SMF30ZNF

binary

Normalization factor for IFA service time. Used to convert between real IFA times and “normalized” IFA times, that is, the equivalent time on a standard CP. Multiply SMF30_TIME_ON_IFA by this value and divide by 256 to calculate the normalized IFA time.

136

SMF30SNF

binary

Normalization factor for zIIP service time. Used to convert between real zIIP times and normalized zIIP times, that is, the equivalent time on a standard CP. Multiply SMF30_TIME_ON_zIIP by this value and divide by 256 to calculate the normalized zIIP time.

Operator Section
This section contains the actions performed by the operator for this address space during the period being reported. Counts are increased by one when the mount is verified. If an incorrect volume is mounted, the count is not increased even though another mount message is issued.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30OOF
Length SMF30OLN
Number SMF30OON - Reports the number of operator sections on the current record. Because only one operator section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30OOF)

SMF30PDM

binary

Number of non-specific DASD mounts.

SMF30PRD

binary

Number of specific DASD mounts.

SMF30PTM

binary

Number of non-specific tape mounts.

SMF30TPR

binary

Number of specific tape mounts.

SMF30MTM

binary

Number of non-specific MSS mounts. As of MVS/SP4.1, this field is no longer valid, and contains zeroes.

SMF30MSR

binary

Number of specific MSS mounts. As of MVS/SP4.1, this field is no longer valid, and contains zeroes.

APPC/MVS Resource Section
This section contains summary data related to how an address space uses APPC/MVS resources. This section will appear on the record only if the address space has used APPC/MVS services and there is data to be reported.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30DRO
Length SMF30DRL
Number SMF30DRN - Reports the number of APPC/MVS resource sections on the current record. Because only one APPC/MVS resource section can appear on the record, this field is ‘1’ (if the section exists) or ‘0’ (if it doesn’t).
(Offset from beginning of record: SMF30DRO)

SMF30DC

binary

Number of conversations, both currently active and deallocated, associated with the transaction program ID.

SMF30DCA

binary

Number of all conversations allocated.

SMF30DSC

binary

Number of times the transaction program issued a Send call. Note: Because an interval or step might end in the middle of a Send call, this field might contain zero while SMF30DDS contains a nonzero value.

SMF30DDS

long

floating point hex Amount of data, in bytes, sent by the transaction program.

SMF30DRC

binary

Number of times the transaction program issued a Receive call. Note: Because an interval or step might end in the middle of a Receive call, this field might contain zero while SMF30DDR contains a nonzero value.

SMF30DDR

long

floating point hex Amount of data, in bytes, received by the transaction program.

SMF30DAC

binary

Number of active conversations.

SMF30DTR

binary

Number of APPC/MVS transactions programs scheduled by the APPC/MVS transaction scheduler (ASCH).

APPC/MVS Cumulative Resource Section
This section contains cumulative summary data related to how an address space uses APPC/MVS resources. Regardless of whether the record is an interval, step termination, or step total record, this section represents cumulative data since the start of the job. This section will only appear on the record if the address space has used APPC/MVS services and there is data to be reported.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30ARO
Length SMF30ARL
Number SMF30ARN - This field will be ‘1’ (if the section is on the record) or ‘0’ (if it isn’t)
(Offset from beginning of record: SMF30ARO)

SMF30CN

binary

Total number of conversations associated with the transaction program (TP) ID, both currently active and deallocated.

SMF30CNA

binary

Total number of all conversations allocated.

SMF30SEN

binary

Total number of times the transaction program (TP) issued a Send call.

SMF30DAT

long

floating point hex Total amount of data sent by the transaction program (TP) in bytes (long floating point).

SMF30REC

binary

Total number of times the transaction program (TP) issued a Receive call.

SMF30DAR

long

floating point hex Total amount of data received by the transaction program (TP) in bytes (long floating point).

SMF30TAC

binary

Total number of active conversations.

SMF30ATR

binary

Total number of APPC/MVS transactions programs scheduled by the APPC/MVS transaction scheduler (ASCH).

z/OS UNIX System Services Process Section
Reports on the use of z/OS UNIX services by z/OS UNIX processes:
(Offset from beginning of record: SMF30OPO)

SMF30OPI

binary

z/OS UNIX System Services process ID.

SMF30OPG

binary

z/OS UNIX System Services process group ID.

SMF30OUI

binary

z/OS UNIX System Services process user ID.

SMF30OUG

binary

z/OS UNIX System Services process user group ID.

SMF30OSI

binary

z/OS UNIX System Services process session ID.

SMF30OSC

binary

Number of z/OS UNIX System Services services requested by the process.

SMF30OST

binary

Total CPU time (in hundredths of a second) accumulated by z/OS UNIX System Services services requested by the process. Note that the value in SMF30OST is already included in fields SMF30CPT or SMF30CPS.

SMF30ODR

binary

Number of z/OS UNIX System Services directory reads for the process.

SMF30OFR

binary

Number of reads from z/OS UNIX System Services HFS regular files.

SMF30OFW

binary

Number of writes to z/OS UNIX System Services HFS regular files.

SMF30OPR

binary

Number of reads from z/OS UNIX System Services HFS pipe.

SMF30OPW

binary

Number of writes to z/OS UNIX System Services HFS pipe.

SMF30OSR

binary

Number of reads from z/OS UNIX System Services HFS special files.

SMF30OSW

binary

Number of writes to z/OS UNIX System Services HFS special files.

SMF30OLL

binary

Number of pathname lookup calls to the logical file system.

SMF30OLP

binary

Number of pathname lookup calls to the physical file system.

SMF30OGL

binary

Number of pathname generation calls to the logical file system.

SMF30OGP

binary

Number of pathname generation calls to the physical file system to determine a pathname.

SMF30OPP

binary

Parent process ID.

SMF30OKR

binary

Number of reads for network socket.

SMF30OKW

binary

Number of writes for network socket.

SMF30OMS

binary

Number of bytes that message queues sent.

SMF30OMR

binary

Number of bytes that message queues received.

SMF30OSY

binary

Number of times the sync() function was called.

Automatic Restart Management Section
This section contains information related to a batch job or started task that registers as an element of automatic restart management. The element name, element type, and timestamps of the completion of various events are recorded. If the timestamp for an event is zero, then that particular event had not been completed by the time the record was generated.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30RMO
Length SMF30RML
Number SMF30RMN
(Offset from beginning of record: SMF30RMO)

SMF30RNM

EBCDIC

Element name.

SMF30RTP

EBCDIC

Element type.

SMF30RRG

EBCDIC

Restart group for element in SMF30RNM.

SMF30RSN

EBCDIC

The system name for the system on which the element was initially started; blank, for the initial start. Note: The current system name is in the SMF30SYN field.

SMF30RGT

binary

The time (local) when the element issued the IXCARM macro with the REGISTER parameter, in hundredths of a second.

SMF30RGD

binary

The date when the element issued the REGISTER request, in the form 0cyydddF.

SMF30RWT

binary

The time (local) when the element issued the IXCARM macro with the WAITPRED parameter, in hundredths of a second. This field will be zero if this function was not requested.

SMF30RWD

binary

The date when the element issued IXCARM with the WAITPRED parameter, in the form 0cyydddF (where ‘F’ is the sign). This field will be zero if this function was not requested.

SMF30RYT

binary

The time (local) when the element issued the IXCARM macro with the READY parameter, in hundredths of a second.

SMF30RYD

binary

The date when this element issued the IXCARM macro with the READY parameter, in the format 0cyydddF (where ‘F’ is the sign).

SMF30RTT

binary

The time (local) when the element was deregistered, in hundredths of a second. This field will be zero if this element is not yet deregistered or if it ended abnormally.

SMF30RTD

binary

The date when this element was deregistered, in the format 0cyydddF. This field will be zero if this element is not yet deregistered or if it ended abnormally.

Usage Data Section
This section contains the product ID information (specified on the REGISTER request of the IFAUSAGE macro) and the usage data that has been collected for the time period (interval, step, or job), for the product in the current address space only.
For registered products with a domain of TASK and a scope of ALL (example, IMS), there will be one usage section in the record for each unique product that is actively registered at the time the specified interval ended (as opposed to any part of the specified interval). In addition, there will be one section in the record for each unique product ID that has deregistered at least once during the specified interval.
Note: The data for deregistered products with a domain of TASK and a scope of FUNCTION is consolidated into one section in the record by unique product id. This is only performed at the specified interval level.
For all other registered products, there will be one section in the record for each unique product ID (owner, name, version, qualifier) that is actively registered for any part of that specified interval.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30UDO
Length SMF30UDL
Number SMF30UDN
(Offset from beginning of record: SMF30UDO)

SMF30UPO

EBCDIC

Product owner or vendor name (specified on the PRODOWNER option of the IFAUSAGE macro).

SMF30UPN

EBCDIC

Product name (specified on the PRODNAME option of the IFAUSAGE macro).

SMF30UPV

EBCDIC

Product version (if specified on the PRODVERS option of the IFAUSAGE macro or ‘NONE’).

SMF30UPQ

EBCDIC

Product qualifier (if specified on the PRODQUAL option of the IFAUSAGE macro or ‘NONE’).

SMF30UPI

EBCDIC

Product ID (if specified on the PRODID option of the IFAUSAGE macro or ‘NONE’).

SMF30UCT

binary

Product TCB Time (in hundredths of a second).

SMF30UCS

binary

Product SRB Time (in hundredths of a second). 64 40 SMF30URD 8 various Product specific resource data (specified on the DATA option on the IFAUSAGE macro FUNCTIONDATA request). SMF30UDF identifies the format of the data in this field.

SMF30UDF

binary

Data format of value in SMF30URD

Value	Meaning
0	No data specified.
1	CPU time in long floating Point (in hundredths of a second).
2	Binary (64-bit).
3	Long floating point.

SMF30UFG

binary

Usage entry flags

Bit	Meaning When Set
0	Unauthorized register
1-7	Unused

binary

Reserved.

Multisystem Enclave Remote System Data Section
This section contains remote system data for each system that executed work under a multisystem enclave.
Triplet Information:
This section is located on the record using the following triplet fields, which are located in the ‘header/self-defining’ section:

Offset SMF30MOF
Length SMF30MLN
Number SMF30MNO
(Offset from beginning of record: SMF30MOF)

SMF30MRS

EBCDIC

System name on which enclaves created by this address space executed.

SMF30MRA

binary

CPU rate adjustment factor for the system named by SMF30MRS. This is the number of sixteenths of one microsecond of CPU time per CPU service unit.

SMF30MRD

binary

CPU time, in hundredths of a second, accumulated by dependent enclaves that executed on the system named by SMF30MRS.

SMF30MRI

binary

CPU time, in hundredths of a second, accumulated by independent enclaves that executed on the system named by SMF30MRS.

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

Spectrum SMF Writer - the 4GL SMF Report Writer.

Example -- Normalizing the EXCP Sections in an SMF Type 30 Record

This example shows how to split each "physical" type 30 SMF record into multiple "logical" records. Each logical record contains just a single EXCP section. Using this logically expanded input file, it is then easy to use the standard 4GL syntax to make useful reports from the array of EXCP data in each type 30 record. (That is because normalization puts a single EXCP section at the same location in each logical record.)

Since the main purpose here is just to illustrate how to normalize an input file, this example simply lists some fields from the EXCP sections of a few records. Specifically, we list the SMF30DEV (device class), SMF30DDN (DDNAME) and SMF30BLK (block count) fields from the EXCP section. The other report fields all come from the constant portion of the SMF 30 record.

By the way, there are many different kinds of variable sections in the SMF type 30 record (not just EXCP sections). For example, there are I/O activity sections, processor accounting sections, performance sections, storage sections and others. You can normalize any of these sections using this same technique with Spectrum Writer. You can even normalize more than one section of the record in the same run.

These Spectrum Writer Control Statements

INPUT: SMF30
       NORMWHEN(SMF30RTY = 30)
       NORMSMF(SMF30EOF)

INCLUDEIF: SMF30RTY = 30     &
           SMF30SID = 'DEV1' &
           SMF30STP = 4

TITLE:     'ADDRESS SPACE ACTIVITY'

COLUMNS:   SMF30DTE SMF30TME SMF30SID SMF30JBN SMF30PGM
           SMF30STM SMF30JNM SMF30DEV SMF30DDN SMF30BLK

SORT:      SMF30DTE SMF30TME

Produce This SMF Type 30 EXCP Details Report


                                      ADDRESS SPACE ACTIVITY

SMF30DTE  SMF30TME   SMF30SID SMF30JBN SMF30PGM SMF30STM SMF30JNM   SMF30DEV SMF30DDN       SMF30BLK
 
07/19/08  6:00:03.48  DEV1    BCA5148  BPXPRECP STEP1    STC07283         32 SYS00001              1
07/19/08  6:00:03.48  DEV1    BCA5148  BPXPRECP STEP1    STC07283         32 SYS00002          6,035
07/19/08  6:00:03.48  DEV1    BCA5148  BPXPRECP STEP1    STC07283         32 SYS00003              2
07/19/08  6:00:03.48  DEV1    BCA5148  BPXPRECP STEP1    STC07283         32 SYS00004          3,078
07/19/08  6:00:03.48  DEV1    BCA5148  BPXPRECP STEP1    STC07283         32 SYS00005             18
07/19/08  6:00:03.48  DEV1    BCA5148  BPXPRECP STEP1    STC07283         32 SYS00006              6
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285          0 SYSOUT                0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285         32 SORTWK01              0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285         32 SORTWK02              0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285         32 SORTWK03              0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285         32 SORTIN                0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285         32 SORTOUT               0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285         32 SYSIN                 0
07/19/08  6:00:14.57  DEV1    SMFSLRD  SORT     SORT     STC07285          0 SORTSNAP              0
07/19/08  6:00:14.57  DEV1    SMFSLRD  IFASMFDP SELESLR  STC07285         64           1,077,952,576
07/19/08  6:00:14.57  DEV1    SMFSLRD  IFASMFDP CLEAR    STC07285         64           1,077,952,576
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284          0 SYSOUT                0
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284         32 SORTWK02              2
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284         32 SORTWK03              2
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284         32 SORTWK04              2
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284       -128 SORTIN            2,239
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284       -128 SORTOUT             102
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284          0 SYSIN                 0
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284          0 SYSPRINT              0
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284          0 SORTMSG               0
07/19/08  6:01:05.38  DEV1    M99RPT12 SORT     STP01020 JOB07284         32 SORTWK01              2
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284          0 SYSOUT                0
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284          0 SYSPRINT              0
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284          0 SORTMSG               0
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284         32 SORTWK01              2
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284         32 SORTWK02              2
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284         32 SORTWK03              2
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284         32 SORTWK04              2
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284         32 SORTIN                1
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284         32 SORTOUT               1
07/19/08  6:01:05.51  DEV1    M99RPT12 SORT     STP01030 JOB07284          0 SYSIN                 0
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284         32 STEPLIB               3
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284         32 MIFI0002              3
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284       -128 MIFO0001         17,774
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284          0 SYSPRINT              0
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284          0 SYSDBOUT              0
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284          0 SYSOUT                0
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284         32 STEPLIB               0
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284         32 LINKL                 0
07/19/08  6:01:27.56  DEV1    M99RPT12 MIFQR11G STP01050 JOB07284       -128 MIFI0001         17,775
. . .

See other sample SMF reports.

SMF Type 30 Record

This table shows the record layout for type 30 SMF records (Common Address Space Work - z/OS 1.10).

It's easy to report on SMF 30 data! (Jump to sample reports)

Example -- Normalizing the EXCP Sections in an SMF Type 30 Record

This table shows the record layout for type 30 SMF records
(Common Address Space Work - z/OS 1.10).