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 30 Record

This table shows the record layout for type 30 SMF records
(Common Address Space Work).

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, started task, or batch job) starts or completes. If you requested interval accounting, a type 30 record is also written when an SMF interval ends. Use the subtype field (SMF30STP) to distinguish between these kinds of type 30 records.

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

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 30 Record -- Common Address Space Work
Offset
(Dec.)		Offset
(Hex)		NameLengthFormatDescription
00SMF30LEN2binary
Record Length. This field along with the next, are referred to as the RDW (record descriptor word). See “Standard SMF Record Header” on page 13-1 for a detailed description.
22SMF30SEG2binary
Segment descriptor (see record length field).
44SMF30FLG1binary
System indicator: Bit Meaning When Set 0 Subsystem identification follows system identification 1 Subtypes used 2 Reserved 3-6 Version indicators* 7 Reserved.*See “Standard SMF Record Header” on page 13-1 for a detailed description.
55SMF30RTY1binary
Record type 30 (X'1E').
66SMF30TME4binary
Time since midnight, in hundredths of a second, that the record was moved to the SMF buffer.
10ASMF30DTE4packed
Date that the record was moved to the SMF buffer, in the form 0cyydddF (in local time). See “Standard SMF Record Header” on page 13-1 for a detailed description.
14ESMF30SID4EBCDIC
System identification (from the SID parameter).
1812SMF30WID4EBCDIC
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).
2216SMF30STP2binary
Record subtype.
Sub
type		Meaning
1Job start or start of other work unit. The subtype 1 record identifies the work unit but contains no resource data.
2Activity since previous interval ended.
3Activity for the last interval before step termination.
4Step total.
5Job termination or termination of other work unit.
6System address space. 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.
2418SMF30SOF4binary
Offset to subsystem section from start of record, including the record descriptor word (RDW).
281CSMF30SLN2binary
Length of subsystem section.
301ESMF30SON2binary
Number of subsystem sections.
3220SMF30IOF4binary
Offset to identification section from start of record, including the record descriptor word (RDW).
3624SMF30ILN2binary
Length of identification section.
3826SMF30ION2binary
Number of identification sections.
4028SMF30UOF4binary
Offset to I/O activity section from start of record, including the record descriptor word (RDW).
442CSMF30ULN2binary
Length of I/O activity section.
462ESMF30UON2binary
Number of I/O activity sections.
4830SMF30TOF4binary
Offset to completion section from start of record, including the record descriptor word (RDW).
5234SMF30TLN2binary
Length of completion section.
5436SMF30TON2binary
Number of completion sections.
5638SMF30COF4binary
Offset to processor section from start of record, including the record descriptor word (RDW).
603CSMF30CLN2binary
Length of processor section.
623ESMF30CON2binary
Number of processor sections.
6440SMF30AOF4binary
Offset to accounting section from start of record, including the record descriptor word (RDW).
6844SMF30ALN2binary
Total length of the single accounting section.
7046SMF30AON2binary
Number of variable length text segments.
7248SMF30ROF4binary
Offset to storage section from start of record, including the record descriptor word (RDW).
764CSMF30RLN2binary
Length of storage section.
784ESMF30RON2binary
Number of storage sections.
8050SMF30POF4binary
Offset to performance section from start of record, including the record descriptor word (RDW).
8454SMF30PLN2binary
Length of the performance section.
8656SMF30PON2binary
Number of performance sections.
8858SMF30OOF4binary
Offset to operator section from start of record, including the record descriptor word (RDW).
925CSMF30OLN2binary
Length of the operator section.
945ESMF30OON2binary
Number of operator sections.
9660SMF30EOF4binary
Offset to the execute channel program (EXCP) section from start of record, including the record descriptor word (RDW).
10064SMF30ELN2binary
Length of the execute channel program (EXCP) section, in this record.
10266SMF30EON2binary
Number of execute channel program (EXCP) sections in this record.
10468SMF30EOR2binary
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.
1066ASMF30RVD2--
Reserved.
1086CSMF30EOS4binary
Number of execute channel program (EXCP) sections in subsequent records.
11270SMF30DRO4binary
Offset to APPC/MVS resource section from start of record, including the record descriptor word (RDW).
11674SMF30DRL2binary
Length of APPC/MVS resource section.
11876SMF30DRN2binary
Number of APPC/MVS resource sections in this record (this number is 0 or 1).
12078SMF30ARO4binary
Offset to APPC/MVS cumulative resource section from start of record, including the record descriptor word (RDW).
1247CSMF30ARL2binary
Length of APPC/MVS cumulative resource section.
1267ESMF30ARN2binary
Number of APPC/MVS cumulative resource sections in this record (this number is 0 or 1).
12880SMF30OPO4binary
Offset to OpenMVS process section.
13284SMF30OPL2binary
Length of OpenMVS process section.
13486SMF30OPN2binary
Number of OpenMVS process sections on current record.
13688SMF30OPM4binary
Number of OpenMVS process sections on subsequent records.
1408CSMF30UDO4binary
Offset to first usage data section from the start of the record, including the record descriptor word (RDW).
14490SMF30UDL2binary
Length of each usage data section - ‘76’.
14692SMF30UDN2binary
Number of usage data sections in this record.
14894SMF30UDS4binary
Number of usage data sections in subsequent records.
15298SMF30RMO4binary
Offset to first automatic restart management section.
1569CSMF30RML2binary
Length of automatic restart management section.
1589ESMF30RMN2binary
Number of automatic restart management sections.
160A0SMF30RMS4binary
Number of automatic restart management sections in subsequent records.
164A4SMF30MOF4binary
Offset to the Multisystem Enclave Remote Data section.
168A8SMF30MLN2binary
Length of MultiSystem Enclave Remote System Data section.
170AASMF30MNO2binary
Number of MultiSystem Enclave Remote System Data sections in this record.
172ACSMF30MOS4binary
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)
00SMF30TYP2binary
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.
22SMF30RS12--
Reserved.
44SMF30RVN2EBCDIC
Record version number Value Meaning C’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
66SMF30PNM8EBCDIC
Subsystem or product name, for example SMF.
14ESMF30OSL8EBCDIC
MVS software level (consists of an acronym and the version, release, and modification level numbers).
2216SMF30SYN8EBCDIC
System name (from the SYSNAME parameter in the IEASYSxx parmlib member).
301ESMF30SYP8EBCDIC
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)
00SMF30JBN8EBCDIC
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.
88SMF30PGM8EBCDIC
Program name (taken from PGM= parameter on EXEC card). If a backward reference was used, this field contains PGM=*.DD.
1610SMF30STM8EBCDIC
Step name (taken from name on EXEC card).
2418SMF30UIF8EBCDIC
User-defined identification field (taken from common exit parameter area, not from USER=parameter on job statement).
3220SMF30JNM8EBCDIC
JES job identifier. Jobs scheduled by the APPC/MVS transaction scheduler (ASCH) start with an “A” followed by a seven-digit number.
4028SMF30STN2binary
Step number (first step = 1, etc.).
422ASMF30CLS1binary
Job class (blank for TSO/E session or started tasks).
432B--1--
Reserved.
442CSMF30PGN2binary
Beginning with z/OS V1R3, this field is always zero.
462ESMF30JPT2binary
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.)
4830SMF30AST4binary
Device allocation start time, in hundredths of a second.
5234SMF30PPS4binary
Problem program start time, in hundredths of a second.
5638SMF30SIT4binary
Time since midnight, in hundredths of a second, that the initiator selected this step or job.
603CSMF30STD4packed
Date that the initiator selected this step, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
6440SMF30RST4binary
Time since midnight, in hundredths of a second, that the reader recognized the JOB card (for this job).
6844SMF30RSD4packed
Date that the reader recognized the JOB card (for this job), in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
7248SMF30RET4binary
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.
764CSMF30RED4packed
Date that the reader recognized the end of the batch job or started task (reader stop date), in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
8050SMF30USR20EBCDIC
Programmer’s name.
10064SMF30GRP8EBCDIC
RACF group ID. 0 = RACF is not active.
1086CSMF30RUD8EBCDIC
RACF user ID. 0 = RACF is not active.
11674SMF30TID8EBCDIC
RACF terminal ID. This field is zero if RACF is not active (or the user is not a terminal user).
1247CSMF30TSN8EBCDIC
Terminal symbolic name.
13284SMF30PSN8EBCDIC
The name of the step that invoked the procedure. This field contains blanks if not part of a procedure.
1408CSMF30CL88EBCDIC
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).
14894SMF30ISS8binary
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.
1569CSMF30IET8binary
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.
164A4SMF30SSN4binary
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.
168A8SMF30EXN16binary
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.

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)
00SMF30INP4binary
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
44SMF30TEP4binary
Total blocks transferred (accumulated execute channel program (EXCP) counts).
88SMF30TPT4binary
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.
12CSMF30TGT4binary
Number of TGETS (terminal reads) for a TSO/E session.
1610SMF30RDR1binary
Reader device class as defined in JESPARMS. 0 — for TSO/E sessions or started tasks.
1711SMF30RDT1binary
Reader device type as defined in JESPARMS. 0 — for TSO/E sessions or started tasks.
1812SMF30TCN4binary
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.
2216SMF30DCF4binary
Flag word Bit Meaning When Set 0 Device connect time may be incorrect 1-31 Reserved.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.
261ASMF30RSB2--
Reserved.
281CSMF30TRR4binary
Total address space REREAD count.
3220SMF30AIC4binary
DASD I/O connect time, in 128-microsecond units, for address space plus dependent enclaves.
3624SMF30AID4binary
DASD I/O disconnect time, in 128-microsecond units, for address space plus dependent enclaves.
4028SMF30AIW4binary
DASD I/O pending plus control unit queue time, in 128-microsecond units, for address space plus dependent enclaves.
442CSMF30AIS4binary
DASD I/O start subchannel count for address space plus dependent enclaves.
4830SMF30EIC4binary
DASD I/O connect time, in 128-microsecond units, for indpendent enclaves owned by the address space.
5234SMF30EID4binary
DASD I/O disconnect time, in 128-microsecond units, for independent enclaves owned by the address space.
5638SMF30EIW4binary
DASD I/O pending plus control unit queue time, in 128-microsecond units, for independent enclaves owned by the address space.
603CSMF30EIS4binary
DASD I/O start subchannel count for independent enclaves.
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)
00SMF30SCC2binary
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).

22SMF30STI2binary
Step/Job termination indicator
BitMeaning When Set
0Reserved
1Canceled by exit IEFUJV
2Canceled by exit IEFUJI
3Canceled by exit IEFUSI
4Canceled by exit IEFACTRT
5Step is to be restarted
6If 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.
7If zero, then normal completion. If 1, then step was flushed.
8EXCP counts might be incorrect because the record did not include all the DD statements.
9Previous interval record was not written because an error occurred. The cumulative count might be incorrect because the counters were cleared.
10EXCP sections were not merged from the interval to the step record or from the step to the job record
11Step completed with a “post execution” error. Post-execution errors include a failure that occurred because the ALLOCxx parmlib member specified CATLG_ERR FAILJOB(YES).
12Step completed due to OpenMVS exec function request.
13JOB 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-15Reserved.
44SMF30ARC4binary
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)
00SMF30PTY2binary
Reserved.
22SMF30TFL2binary
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.
44SMF30CPT4binary
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. 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 IFACROSSOVER=NO in the IEAOPTxx parmlib member.
88SMF30CPS4binary
Step CPU time under the service request block (SRB), in hundredths of a second.
12CSMF30ICU4binary
Initiator CPU time under the task control block (TCB), in hundredths of a second. This field is set at step termination.
1610SMF30ISB4binary
Initiator CPU time under the service request block (SRB), in hundredths of a second. This field is set at step termination.
2014SMF30JVU4binary
Step vector CPU time, in hundredths of a second.
2418SMF30IVU4binary
Initiator vector CPU time, in hundredths of a second. This field is set at step termination.
281CSMF30JVA4binary
Step vector affinity time, in hundredths of a second.
3220SMF30IVA4binary
Initiator vector affinity time, in hundredths of a second. This field is set at step termination.
3624SMF30IST4binary
Interval start time for type 30 subtype 2 and 3 records, in hundredths of a second.
4028SMF30IDT4packed
Interval start date for type 30 subtype 2 and 3 records, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
442CSMF30IIP4binary
Amount of CPU time used to process I/O interrupts, in hundredths of a second.
4830SMF30RCT4binary
Amount of CPU time used by the region control task (RCT), in hundredths of a second.
5234SMF30HPT4binary
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.
5638SMF30CSC4binary
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).
603CSMF30DMI4binary
ADMF-Number of pages moved with ADMF WRITE operation.
6440SMF30DMO4binary
ADMF-Number of pages moved with ADMF READ operation.
6844SMF30ASR4binary
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.
7248SMF30ENC4binary
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.
764CSMF30DET4binary
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.
8050SMF30CEP4binary
CPU time consumed for an address space or job while enqueue promoted (in 1.024 millisecond units).
8252SMF30TF22binary
Additional timer flags Bit Meaning When Set 0 SMF30_TIME_ON_IFA has an invalid value due to a timer value calculation error. 1 SMF30_ENCLAVE_TIME_ON_IFA has an invalid value due to a timer value calculation error. 2 SMF30_DEP_ENCLAVE_TIME_ON_IFA has an invalid value due to a timer value calculation error. 3 SMF30_TIME_IFA_ON_CP has an invalid value due to a timer value calculation error. 4 SMF30_ENCLAVE_TIME_IFA_ON _CP has an invalid value due to a timer value calculation error. 5 SMF30_DEP_ENCLAVE_TIME_IFA_ON _CP has an invalid value due to a timer value calculation error.
8454SMF30_
TIME_
ON_
IFA		4binary
CPU time spent on IFA in hundredths of a second (including enclave time).
8858SMF30_
ENCLAVE_
TIME_
ON_
IFA		4binary
Enclave time spent on IFA in hundredths of a second.
925CSMF30_
DEP_
ENCLAVE_
TIME_
ON_
IFA		4binary
Dependent enclave time spent on IFA in hundredths of a second.
9660SMF30_
TIME_
IFA_
ON_
CP		4binary
CPU time spent running IFA eligible work on a standard CP in hundredths of a second (including enclave time).
10064SMF30_
ENCLAVE_
TIME_
IFA_
ON_
CP		4binary
IFA Enclave time spent on a standard CP in hundredths of a second.
10468SMF30_
DEP_
ENCLAVE_
TIME_
IFA_
ON_
CP		4binary
IFA Dependent enclave time spent on a standard CP in hundredths of a second.
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.

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.
(Offset from beginning of record: SMF30EOF)
00SMF30DEV1binary
Device class.
11SMF30UTP1binary
Unit type.
22SMF30CUA2binary
Device number.
44SMF30DDN8EBCDIC
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.
12CSMF30BLK4binary
Count of blocks issued for the device against the data set.
1610SMF30BSZ2binary
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. 1-15 Largest blocksize of the data set.
1812SMF30DCT4binary
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.
2218SMF30XBS8binary
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)
00SMF30ACL1binary
Length of accounting section (excluding this field).
11SMF30ACTvariableEBCDIC
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)
00SMF30RSV2Reserved.
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.
22SMF30SFL1binary
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.
33SMF30SPK1binary
Storage protect key, in the form xxxx0000 where xxxx is the key.
44SMF30PRV2binary
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.
66SMF30SYS2binary
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.
88SMF30PGI4binary
Number of pages that were paged in from auxiliary storage.
12CSMF30PGO4binary
Number of pages that were paged out to auxiliary storage.
1610SMF30CPM4binary
Number of attempts to read data from an ESO hiperspace that were not satisfied because the data has been deleted.
2014SMF30NSW4binary
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.)
2418SMF30PSI4binary
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).
281CSMF30PSO4binary
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.
3220SMF30VPI4binary
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.
3624SMF30VPO4binary
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.
4028SMF30VPR4binary
Number of VIO reclaims.
442CSMF30CPI4binary
Number of common area page-ins (LPA + CSA) from auxiliary storage to central storage.
4830SMF30HPI4binary
Number of hiperspace page-ins from auxiliary to processor storage.
5234SMF30LPI4binary
Number of LPA page-ins from auxiliary storage to central storage.
5638SMF30HPO4binary
Number of hiperspace page-outs from processor to auxiliary storage.
603CSMF30PST4binary
Number of pages stolen from this address space.
6440SMF30PSC8binary
Number of CPU page seconds for this address space, in page millisecond units. (A page millisecond unit equals 1.024 milliseconds.)
7248SMF30RGB4binary
Private area size in bytes (less than 16 megabytes).
7640SMF30ERG4binary
Private area size in bytes (greater than 16 megabytes).
8050SMF30ARB4binary
Maximum virtual storage in bytes allocated from the local system queue area (LSQA) and the SWA subpools (less than 16 megabytes).
8454SMF30EAR4binary
Maximum virtual storage in bytes allocated from the local system queue area (LSQA) and the SWA subpools (greater than 16 megabytes).
8858SMF30URB4binary
Maximum virtual storage in bytes allocated from the user subpools (less than 16 megabytes).
925CSMF30EUR4binary
Maximum virtual storage in bytes allocated from the user subpools (greater than 16 megabytes).
9660SMF30RGN4binary
Region size established, in 1K units, rounded up to a 4K boundary. The contents of this field is determined as follows: v 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. v 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).v 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.
10064SMF30DSV4binary
Amount of user key data space and hiperspace virtual storage (high water mark) used during the step/job (in megabytes).
10468SMF30PIE4binary
Number of unblocked pages that were paged in from expanded storage.
1086CSMF30POE4binary
Number of unblocked pages that were paged out to expanded storage.
11270SMF30BIA4binary
Number of blocked pages that were paged in from auxiliary storage.
11674SMF30BOA4binary
Number of blocked pages that were paged out to auxiliary storage.
12078SMF30BIE4binary
Number of blocked pages that were paged in from expanded storage.
1247CSMF30BOE4binary
Number of blocked pages that were paged out to expanded storage.
12880SMF30KIA4binary
Number of blocks that were paged in from auxiliary storage.
13284SMF30KOA4binary
Number of blocks that were paged out to auxiliary storage.
13688SMF30KIE4binary
Number of blocks that were paged in from expanded storage.
1408CSMF30KOE4binary
Number of blocks that were paged out to expanded storage.
14490SMF30PSF8binary
Number of CPU page seconds for the IARVSERV shared central storage frames in use by this address space, in page milliseconds.
15298SMF30PAI4binary
Number of IARVSERV shared pages that were paged in from auxiliary storage in this address space.
1569CSMF30PEI4binary
Number of IARVSERV shared pages that were paged in from expanded storage in this address space.
160A0SMF30ERS8binary
Expanded storage page residency time in page-milliseconds.
168A8SMF30MEM8binary
Memlimit value (in MB).
176B0SMF30MLS1binary
Source of Memlimit, which is one of the following: Value Meaning 01 MEMLIMIT set by SMF. 02 MEMLIMIT set explicitly in the JCL with MEMLIMIT parameter on JOB or EXEC statement. 03 MEMLIMIT is unlimited based on REGION=0 specification. 04 MEMLIMIT set by IEFUSI.
177B1SMF30RESX23--
Reserved.
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)
00SMF30SRV4binary
Total service units.
44SMF30CSU4binary
CPU service units.
88SMF30SRB4binary
Service request block (SRB) service units.
12CSMF30IO4binary
I/O service units.
1610SMF30MSO4binary
Main storage occupancy (MSO) service units.
2014SMF30TAT4binary
System resources manager (SRM) transaction active time, in 1024-microsecond units.
2418SMF30SUS4binary
Copy of RmctAdjC when this SMF record was produced, number of sixteenths of one CPU microsecond per CPU service unit.
281CSMF30RES4binary
System resources manager (SRM) transaction residency time, in 1024-microsecond units. That is the amount of time the SRM transaction was in real storage.
3220SMF30TRS4binary
Number of system resources manager (SRM) transactions.
3624SMF30WLM8EBCDIC
Workload name. This field is blank (X‘40’) when in workload management compatibility mode.
442CSMF30SCN8EBCDIC
Service class name. This field will contain ’SYSOTHER’ during the time of a WLM POLICY switch.
5234SMF30GRN8EBCDIC
Resource group name.
603CSMF30RCN8EBCDIC
Report class name. This field is blank (X‘40’) during the time of a WLM POLICY switch.
6844SMF30ETA4binary
Independent enclave transaction active time in 1024-microsecond units.
7248SMF30ESU4binary
Independent enclave CPU service units.
764CSMF30ETC4binary
Independent enclave transaction count.
8050SMF30PFL16EBCDIC
Scheduling environment name. Binary zeros if no scheduling environment is specified.
9660SMF30JQT4binary
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. It is available with OS/390 JES2 Release 4 and higher.
10064SMF30RQT4binary
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. It is available on OS/390 JES2 Release 4 and higher.
10468SMF30HQT4binary
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. It is available with OS/390 JES2 Release 4 and higher.
1086CSMF30SQT4binary
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. Prior to OS/390 JES2 Release 4, and for all JES3 releases, this field includes time the job was ineligible for execution.
11270SMF30PF11EBCDIC
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.
11371SMF30PF21EBCDIC
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.
11472SMF30RS42EBCDIC
Reserved.
11674SMF30JPN8EBCDIC
Subsystem collection name from IWMCLSFY SUBCOLN
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)
00SMF30PDM4binary
Number of non-specific DASD mounts.
44SMF30PRD4binary
Number of specific DASD mounts.
88SMF30PTM4binary
Number of non-specific tape mounts.
12CSMF30TPR4binary
Number of specific tape mounts.
1610SMF30MTM4binary
Number of non-specific MSS mounts. As of MVS/SP4.1, this field is no longer valid, and contains zeroes.
2014SMF30MSR4binary
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)
00SMF30DC4binary
Number of conversations, both currently active and deallocated, associated with the transaction program ID.
44SMF30DCA4binary
Number of all conversations allocated.
88SMF30DSC4binary
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.
12CSMF30DDS8long
floating point hex Amount of data, in bytes, sent by the transaction program.
2014SMF30DRC4binary
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.
2418SMF30DDR8long
floating point hex Amount of data, in bytes, received by the transaction program.
3220SMF30DAC4binary
Number of active conversations.
3624SMF30DTR4binary
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)
00SMF30CN4binary
Total number of conversations associated with the transaction program (TP) ID, both currently active and deallocated.
44SMF30CNA4binary
Total number of all conversations allocated.
88SMF30SEN4binary
Total number of times the transaction program (TP) issued a Send call.
12CSMF30DAT8long
floating point hex Total amount of data sent by the transaction program (TP) in bytes (long floating point).
2014SMF30REC4binary
Total number of times the transaction program (TP) issued a Receive call.
2418SMF30DAR8long
floating point hex Total amount of data received by the transaction program (TP) in bytes (long floating point).
3220SMF30TAC4binary
Total number of active conversations.
3624SMF30ATR4binary
Total number of APPC/MVS transactions programs scheduled by the APPC/MVS transaction scheduler (ASCH).
OpenMVS Process Section

Reports on OpenMVS processes’ use of OpenMVS services.

(Offset from beginning of record: SMF30OPO)
00SMF30OPI4binary
OpenMVS process ID.
44SMF30OPG4binary
OpenMVS process group ID.
88SMF30OUI4binary
OpenMVS process user ID.
12CSMF30OUG4binary
OpenMVS process user group ID.
1610SMF30OSI4binary
OpenMVS process session ID.
2014SMF30OSC4binary
Number of OpenMVS services requested by the process.
2418SMF30OST4binary
Total CPU time (in hundredths of a second) accumulated by OpenMVS services requested by the process.
281CSMF30ODR4binary
Number of OpenMVS directory reads for the process.
3220SMF30OFR4binary
Number of reads from OpenMVS HFS regular files.
3624SMF30OFW4binary
Number of writes to OpenMVS HFS regular files.
4028SMF30OPR4binary
Number of reads from OpenMVS HFS pipe.
442CSMF30OPW4binary
Number of writes to OpenMVS HFS pipe.
4830SMF30OSR4binary
Number of reads from OpenMVS HFS special files.
5234SMF30OSW4binary
Number of writes to OpenMVS HFS special files.
5638SMF30OLL4binary
Number of pathname lookup calls to the logical file system.
603CSMF30OLP4binary
Number of pathname lookup calls to the physical file system.
6440SMF30OGL4binary
Number of pathname generation calls to the logical file system.
6844SMF30OGP4binary
Number of pathname generation calls to the physical file system to determine a pathname.
7248SMF30OPP4binary
Parent process ID.
764CSMF30OKR4binary
Number of reads for network socket.
8050SMF30OKW4binary
Number of writes for network socket.
8454SMF30OMS4binary
Number of bytes that message queues sent.
8858SMF30OMR4binary
Number of bytes that message queues received.
925CSMF30OSY4binary
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)
00SMF30RNM16EBCDIC
Element name.
1610SMF30RTP8EBCDIC
Element type.
2418SMF30RRG16EBCDIC
Restart group for element in SMF30RNM.
4028SMF30RSN8EBCDIC
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.
4830SMF30RGT4binary
The time (local) when the element issued the IXCARM macro with the REGISTER parameter, in hundredths of a second.
5234SMF30RGD4binary
The date when the element issued the REGISTER request, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
5638SMF30RWT4binary
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.
603CSMF30RWD4binary
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.
6440SMF30RYT4binary
The time (local) when the element issued the IXCARM macro with the READY parameter, in hundredths of a second.
6844SMF30RYD4binary
The date when this element issued the IXCARM macro with the READY parameter, in the format 0cyydddF (where ‘F’ is the sign).
7248SMF30RTT4binary
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.
764CSMF30RTD4binary
The date when this element was deregistered, in the format 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description. 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)
00SMF30UPO16EBCDIC
Product owner or vendor name (specified on the PRODOWNER option of the IFAUSAGE macro).
1610SMF30UPN16EBCDIC
Product name (specified on the PRODNAME option of the IFAUSAGE macro).
3220SMF30UPV8EBCDIC
Product version (if specified on the PRODVERS option of the IFAUSAGE macro or ‘NONE’).
4028SMF30UPQ8EBCDIC
Product qualifier (if specified on the PRODQUAL option of the IFAUSAGE macro or ‘NONE’).
4830SMF30UPI8EBCDIC
Product ID (if specified on the PRODID option of the IFAUSAGE macro or ‘NONE’).
5638SMF30UCT4binary
Product TCB Time (in hundredths of a second).
603CSMF30UCS4binary
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.
7248SMF30UDF1binary
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.
7349SMF30UFG1binary
Usage entry flags Bit Meaning when set 0 Unauthorized register 1-7 Unused
744A--2binary
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)
00SMF30MRS8EBCDIC
System name on which enclaves created by this address space executed.
88SMF30MRA4binary
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.
12CSMF30MRD4binary
CPU time, in hundredths of a second, accumulated by dependent enclaves that executed on the system named by SMF30MRS.
1610SMF30MRI4binary
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.

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.

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