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 99 Record (Subtype 12) - z/OS 2.4

This table shows the record layout for type 99 SMF records
(System Resource Manager (SRM) Decisions - z/OS 2.4).

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

Purpose: This record type is written by the SRM component. The records contain:

  • Performance data for each service class period
  • Trace codes representing the SRM actions
  • The data which SRM used to decide which actions to take
  • The controls SRM is using to manage work.

In addition, subtypes 1 and 9 will be written by the SRM component when running in compatibility mode.

Record 99 has the following subtypes:

Subtype 1 Contains system level data, the trace of SRM actions, and data about resource groups. The SRM actions are recorded in trace codes. All trace codes are described in z/OS MVS Programming: Workload Management Services. A subtype 1 record is written every policy interval.

Subtype 2 Contains data for service classes. A subtype 2 record is written every policy interval for each service class if any period in the service class had recent activity.

Subtype 3 Contains service class period plot data. A subtype 3 record is written every policy interval for each service class if any period in the service class had recent activity and plot data.

Subtype 4 Contains information about a device cluster. A device cluster is a set of service classes that compete to use the same non-paging DASD devices. A subtype 4 record is written every policy interval for each device cluster in the system.

Subtype 5 Contains data about monitored address spaces. A subtype 5 record is written each policy interval for each swapped in monitored address space.

Subtype 6 Contains summary information about each service class period, including the resource control settings for the next policy interval. A subtype 6 record is written each policy interval.

Subtype 7 Contains summary information for the Enterprise Storage Server (ESS) with Parallel Access Volume (PAV) feature. A subtype 7 record is written every third policy interval.

Subtype 8 Contains summary information for LPAR CPU management. A subtype 8 record is written each policy interval, when in LPAR mode.

Subtype 9 Contains summary information for dynamic channel path management. A subtype 9 record is written each policy interval.

Subtype 10 Contains information about dynamic processor speed changes. A subtype 10 record is written for every processor speed change.

Subtype 11 Contains information about Group Capacity Limits. A subtype 11 record is written every 5 minutes.

Subtype 12 Subtype 12 contains HiperDispatch interval data. A set of subtype 12 records is written each policy interval.

Note: In some of the following subtype 12 field descriptions, the term "CPU/core" indicates the applicability of the text, as follows:

-- When the multithreading facility is not installed or when the facility is installed but not enabled, the field descriptions relate to logical or physical CPUs.

-- When the multithreading facility is installed and enabled, the field descriptions relate to logical or physical cores.

Subtype 13 Contains information about HiperDispatch. This information is for IBM internal use only.

Subtype 14 Contains HiperDispatch topology data. Subtype 14 records are written every 5 minutes, or in the current policy interval, if a HiperDispatch topology change happened.

It's easy to report on SMF 99 data!

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

Spectrum SMF Writer handles the difficult SMF record parsing for you automatically. You just specify which fields you want to see.

Spectrum SMF Writer also converts the arcane date and time fields and reformats them into an attractive report.

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

SMF Type 99 Record -- System Resource Manager (SRM) Decisions - z/OS 2.4
Offset
(Dec.)
Offset
(Hex)
NameLengthFormatDescription
00SMF99S12_
LEN
2binary
Record length. This field and the next field (total of four bytes) form the RDW (record descriptor word). See “Standard SMF Record Header” on page 13-1 for a detailed description.
22SMF99S12_
SEG
2binary
Segment descriptor (see record length field).
44SMF99S12_
FLG
1binary
System indicator: Bit Meaning When Set 0-2 Reserved 3-6 Version indicators* 7 Reserved.*See “Standard SMF Record Header” on page 13-1 for a detailed description.
55SMF99S12_
RTY
1binary
Record type 99
66SMF99S12_
TME
4binary
Time since midnight, in hundredths of a second, that the record was moved into the SMF buffer.
100ASMF99S12_
DTE
4packed
Date when the record was moved into the SMF buffer, in the form 0cyydddF. See “Standard SMF Record Header” on page 13-1 for a detailed description.
140ESMF99S12_
SID
4EBCDIC
System identification (from the SID parameter).
1812SMF99S12_
SSID
4EBCDIC
Sub system identification
2216SMF99S12_
TID
2binary
Record subtype (must be at offset X'16' x).
2418SMF99S12_
SDEF_
LEN
4binary
Length of the self definition section.
Self-Defining Section
(Offset from beginning of record: 28)
00SMF99S12_
POF
4binary
Offset to the product section from the beginning of the record (including RDW).
44SMF99S12_
PLN
2binary
Length of the product section.
66SMF99S12_
PON
2binary
Number of the product section.
88SMF99S12_
DOF
4binary
Offset to data section from beginning of the record (including RDW).
12CSMF99S12_
DLN
2binary
Length of the data section.
14ESMF99S12_
DON
2binary
Number of the data section.
SMF 99 Product Information
(Offset from beginning of record: SMF99S12_POF)
00SMF99S12_
VN2
2binary
Record sub-version. Use to identify changes to the record in the service stream.
22SMF99S12_
RVN
2binary
Record version number.
44SMF99S12_
PNM
8EBCDIC
Product name - SRM
12CSMF99S12_
SLV
8EBCDIC
System level from which record was cut (Copied from CVTPRODN).
2014SMF99S12_
SNM
8EBCDIC
System name from which record was cut (Copied from CVTSNAME)
281CSMF99S12_
PFLG
1binary
Record Flags: Bit Meaning When Set 0 Only a subset of the available data was written to avoid that this record gets larger than 32 KByte 1 Only a subset of the available data is written to this record. The rest follows in subsequent records. This record contains a reassembly area. 2–7 Reserved.
291D--3EBCDIC
Reserved.
Subtype 12 - Self Defining Section
(Offset from beginning of record: SMF99S12_DOF)
00SMF9912_
HD_
Int_
Hdr_
OFFSET
4binary
Offset to header data section
44SMF9912_
HD_
Int_
Hdr_
LENGTH
2binary
Length of header data section
66SMF9912_
HD_
Int_
Hdr_
NUMBER
2binary
Number of header data sections
88SMF9912_
HD_
Cap_
Hdr_
OFFSET
4binary
Offset to capacity data section
12CSMF9912_
HD_
Cap_
Hdr_
LENGTH
2binary
Length of capacity data section
14ESMF9912_
HD_
Cap_
Hdr_
NUMBER
2binary
Number of capacity data sections
1610SMF9912_
HD_
Proc_
Hdr_
OFFSET
4binary
Offset to processor data section
2014SMF9912_
HD_
Proc_
Hdr_
LENGTH
2binary
Length of processor data section
2216SMF9912_
HD_
Proc_
Hdr_
NUMBER
2binary
Number of processor data sections
Subtype 12 - Header data section
(Offset from beginning of record: SMF9912_HD_Int_Hdr_OFFSET)
00SMF99C_
VCM_
SMF_
Sequ
4binary
HiperDispatch SMF sequence number
44SMF99C_
VCM_
ErrorCode
2binary
HiperDispatch Error Code
66--1binary
Reserved
77SMF99C_
VCM_
Diag204_
Flags
1binary
Flags
Bit Meaning When Set
0 LPAR capped by WLM
1 LPAR capped by customer
2 Wait Completion
88SMF99C_
VCM_
Interval_
Len
4binary
Measured interval length in microseconds
12CSMF99C_
VCM_
LparPhysProcShr
4binary
LPAR physical processor share for general CPs scaled by 256
1610SMF99C_
VCM_
Interval_
TOD
8binary
TOD when HiperDispatch code got control. In STCK format
2418SMF99C_
VCM_
Flags
4binary
HiperDispatch (HD) status flags
2418SMF99C_
VCM_
Flag1
1binary
1st flag byte
Bit Meaning When Set
0 topology has changed
1 rebuild affinity nodes
2 honor priority has changed
3 dispatcher WUQ error
4 processor speed change
5-7 reserved
2519SMF99C_
VCM_
Flag2
1binary
2nd flag byte
Bit Meaning When Set
0 CEC capacities are valid
1 LPAR capacities are valid
2 Old VCM state
3 reserved
4 dispatcher affinity was updated
5 PTF was issued to initiate a switch into the opposite mode. However, the PTF return info tells us that we are already in the requested mode
6 VCM is transitioning to/from vertical
7 reserved
261ASMF99C_
VCM_
Flag3
1binary
3rd flag byte
Bit Meaning When Set
0 topology facility installed
1 IFA facility installed
2 LPAR has only dedicated CPs
3 Cross memory set
4 new container TLE
5 CPU type has changed
6 Write TopoChg section
7 reserved
271BSMF99C_
VCM_
Flag4
1binary
4th flag byte
Bit Meaning When Set
0 IFA honor priority state of previous interval
1 SUP honor priority state of previous interval
2-7 reserved
281C--4binary
Reserved
3220SMF99C_
VCM_
DiagMPWQ
16structure
1st data element of diagnostic MPWQ data array 48 30 16 structure 2nd data element of diagnostic MPWQ data array
6440SMF99C_
VCM_
DiagECPX
16structure
1st data element of diagnostic ECPX data array 80 50 16 structure 2nd data element of diagnostic
9660SMF99C_
MT_
Flags
4binary
HiperDispatch (HD) MT status flags
9660SMF99C_
MT_
Flag1
1binary
1st MT flag byte:
Bit Meaning When Set
0 Processor resource is viewed as a CPU core.
1 Multiple CPUs defined within a CPU core.
2-3 Reserved.
4 HiperDispatch is now ready for MT mode switches.
5-7 Reserved.
9761SMF99C_
MT_
Flag2
1binary
2nd MT flag byte:
Bit Meaning when set
0 MT mode change is pending due to STSI.
1 The supervisor-requested MT reconfiguration is pending.
2 MT mode change is pending due to HISMT recovery.
3 MT mode change is pending due to wait completion status change.
4 MT mode change is pending due to supervisor request.
5-7 Reserved.
9862--2binary
Reserved.
10064SMF99C_
VCM_
current_
state
4binary
Current HiperDispatch state.
10468SMF99C_
VCM_
previous_
state
4binary
Previous HiperDispatch state.
1086CSMF99C_
VCM_
Restart_
Ctr
4binary
Recovery restart counter.
11270SMF99C_
VCM_
HardwareGroupname
8EBCDIC
Hardware group name 120 78 * 2 binary Internal use by IBM Offset Name Length Format Description
Subtype 12 - Capacity data
(Offset from beginning of record: SMF9912_HD_Int_Cap_OFFSET)
00SMF99C_
HD_
Int_
Cap_
ProcType
1binary
Processor type.
11--15binary
Reserved.
1610SMF99C_
VCM_
LparFlags
1binary
LPAR Status Flags
Bit Meaning when set
0 The physical CPU/core share matches the number and polarization of the CPUs/cores passed by the topology information.
1 The physical CPU/core share is higher than the number of VHs and VMs passed by the topology info.
2 The physical CPU/core share is lower than the number of VHs and VMs passed by the topology info.
3-7 Reserved.
1711--3binary
Reserved.
2014SMF99C_
VCM_
MvsBusyDynaThrUnpark
2binary
Dynamic MvsBusy threshold for unparking, scaled by 16.
2216SMF99C_
VCM_
MvsBusyDynaThrPark
2binary
Dynamic MvsBusy threshold for parking, scaled by 16.
2418SMF99C_
VCM_
MvsBusyThrUnpark
2binary
MvsBusy threshold for unparking, scaled by 16.
261ASMF99C_
VCM_
MvsBusyThrPark
2binary
MvsBusy threshold for parking, scaled by 16.
281CSMF99C_
VCM_
MvsBusy
4binary
Average CPU usage, scaled by 16.
3220SMF99C_
VCM_
LparCapUsedAdj
4binary
Used LPAR capacity in microseconds, adjusted to the scheduled VCM interval length.
3624SMF99C_
VCM_
LparCapUsed
4binary
Used LPAR capacity in microseconds.
4028SMF99C_
VCM_
LparCapUsedDiscr
4binary
Used capacity of the non-guaranteed capacity (partially VM and unparked VLs) in microseconds, adjusted to the scheduled VCM interval length.
442CSMF99C_
VCM_
LparCapUsedVmVl
4binary
Used capacity on VMs and VLs, adjusted to the scheduled VCM interval length.
4830SMF99C_
VCM_
LowCECMaxUp
2binary
Maximum number of VLs unparked if low CEC utilization.
5032SMF99C_
VCM_
LowCECMvsBusy
2binary
Park threshold for low CEC utilization, scaled by 16
5234SMF99C_
VCM_
LparCap_
VmVlUsedLparCapUsedOfAlloc
4binary
Percentage used of allocated VM + VL capacity, scaled by 256.
5638SMF99C_
VCM_
LparCapVmVlUsedOverGuaran
4binary
Percentage of guaranteed VM capacity used by VM + VL, scaled by 256.
603CSMF99C_
VCM_
LparCapAllocVmVl
4binary
Allocated LPAR capacity on VMs and VLs in microseconds.
6440SMF99C_
VCM_
LparCapAlloc
4binary
Allocated LPAR capacity in microseconds. The allocated capacity is provided by the guaranteed capacity on VHs and VMs, plus extra capacity on VMs and unparked VLs.
6844SMF99C_
VCM_
LparCapNonGuaran
4binary
Non guaranteed LPAR capacity in microseconds.
7248SMF99C_
VCM_
LparCapMedGuaran
4binary
Guaranteed LPAR capacity on VMs in microseconds.
764CSMF99C_
VCM_
LparCapGuaran
4binary
Guaranteed LPAR capacity in microseconds. This value is calculated from the physical processor share of this LPAR.
8050SMF99C_
VCM_
MvsBusyProjected
4binary
Projected MvsBusy, scaled by 16.
8454SMF99C_
VCM_
LparUnusedCapShare
4binary
Unused capacity share of this LPAR in microseconds.
8858SMF99C_
VCM_
LparUnusedCap
4binary
Unused LPAR capacity in microseconds including the unused capacity share for this LPAR.
925CSMF99C_
VCM_
CECUtilPark
2binary
CEC Utilization threshold for parking, scaled by 256.
945ESMF99C_
VCM_
PUpDispl
2binary
Park / Unpark displacement, scaled by 16
9660SMF99C_
VCM_
Diag204_
LogInfo
16binary
LPAR information.
9660SMF99C_
VCM_
D204_
TotalW
4binary
Total LPAR weight.
10064SMF99C_
VCM_
D204_
CurrentW
4binary
Current LPAR weight.
10468SMF99C_
VCM_
D204_
WrkCurrW
4binary
Accumulated current LPAR weight.
1086CSMF99C_
VCM_
D204_
LCpus
2binary
Number of logical CPUs/cores for this LPAR.
1106ESMF99C_
VCM_
D204_
Flags1
1binary
LPAR Status flags
Bit Meaning when set
0 LPAR capped by customer per processor type.
1-7 Reserved.
1116F--1binary
Reserved.
11270SMF99C_
VCM_
CpuHi
1binary
Number of VHs.
11371SMF99C_
VCM_
CpuMed
1binary
Number of VMs.
11472SMF99C_
VCM_
CpuLo
1binary
Number of VLs.
11573SMF99C_
VCM_
CpuLoUnparked
1binary
Number of unparked VLs.
11674SMF99C_
VCM_
CpuLoParked
1binary
Number of parked VLs.
11775--11binary
Reserved.
12880SMF99C_
VCM_
DiagCapAdj
16binary
Diagnose information capacity adjustment.
12880SMF99C_
VCM_
DiagCapFlags
4binary
Capacity change flags.
12880SMF99C_
VCM_
DiagCapIncr
2binary
Capacity increase flags
Bit Meaning when set
0 Adjust capacity increase.
1 Adjust capacity increase by unparking a processor.
2 Unpark request.
3 Unpark all request.
4 Reserved.
5 Unpark requested because the LPAR capacity is below the guaranteed capacity + unused capacity share.
6 PR/SM capped LPAR: Unpark requested because of high VH utilization.
7-15 Reserved. Offset Name Length Format Description
Subtype 12 - Processor data section
(Offset from beginning of record: SMF9912_HD_Int_Proc_OFFSET)
00SMF99C_
HD_
Int_
Proc_
Idx
2binary
HiperDispatch interval processor index
22SMF99C_
LCCADSF2
1binary
Processor flag 1 Bit Meaning When Set 0 Reserved 1 Processor parked 2-7 Reserved
33SMF99C_
LCCASCFL
1binary
Processor flag 2 Bit Meaning When Set 0-6 Reserved 7 Processor park request pending 4 4 * 12 HEX Reserved

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

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