Note: Beginning with z/OS® V1R3, WLM compatibility mode
is no longer available. Accordingly, subtypes 1 and 2 of record type
72 are no longer valid and have been removed from this documentation.
Record type 72 has the following subtypes:
- Subtype 3: Workload Activity — is written for each
service class and active report class in the active service policy.
A report class becomes active as soon as work has been assigned to
that report class.
- Workload Manager control section
- Identifies the policy, workload and service/report class name
and contains workload data.
- Service Class Served data section
- Contains information about the service classes being served.
- Resource Group data section
- Contains information about the resource group to which the service
class belongs.
- Service/Report Class Period data section
- Contains goals and actual measured values for each service and
report class period. In addition, there are pointers to the corresponding
Response Time Distribution data section and Work/Resource Manager
State section.
- Response Time Distribution data section
- Contains the response time distribution map and count tables for
each service class period with a response time goal or execution velocity
goal.
- Work/Resource Manager State section
- Contains the subsystem work manager delay array with two entries
for each subsystem.
- Subtype 4: Storage Data — is written from the Monitor
III data gatherer for each service class period of each service class
defined in the active service policy.
- Service Class Period data section
- Contains Monitor III specific using and delay counts and storage
frame counts for each service class period.
- Swap Reason data section
- Contains swap reason information.
- Subtype 5: Serialization Delay — is written from
the Monitor III data gatherer. It contains serialization delay data
on address space level, used as input for the RMF™ Postprocessor to create the Serialization
Delay Report. One record is written for each measurement interval
and when the session terminates.
Subtype 5 contains one control
section and several data sections. While the Serialization control
section contains summary data for system-wide serialization
delays, the data sections contain serialization delay data for up
to twenty address spaces sorted by total contention time.
The GRS
QScan Statistics data section contains measurements about
GQSCAN and ISGQUERY REQINFO=QSCAN requests used to obtain the status
of resources and requestors of those resources. This section contains
data for up to twenty address spaces sorted by the total request execution
time.
- Serialization control section
- Contains system-wide serialization delay data (see Serialization Control Section).
- CMS Lock data section
- Contains CMS lock data per address space. This section is mapped
by CMS lock type data.
- CMS Enqueue/Dequeue Lock data section
- Contains CMS ENQ/DEQ lock data per address space. This section
is mapped by CMS lock type data.
- CMS Latch Lock data section
- Contains CMS Latch lock data per address space. This section is
mapped by CMS lock type data.
- CMS SMF Lock data section
- Contains CMS SMF lock data per address space. This section is
mapped by CMS lock type data.
- Local Lock data section
- Contains local lock data per address space (see Local Lock Data Section).
- CML Lock Owner data section
- Contains CML lock owner data per address space (see CML lock owner data section).
- CML Lock Requestor data section
- Contains CML lock requestor data per address space (see CML Lock Requestor Data Section).
- GRS Latch Set Creator data section
- Contains GRS latch set creator data per address space. This section
is mapped by GRS latch type data.
- GRS Latch Requestor data section
- Contains GRS latch requestor data per address space. This section
is mapped by GRS latch type data.
- GRS Enqueue Step data section
- Contains data for GRS ENQ SCOPE=STEP requests per address space.
This section is mapped by GRS enqueue data.
- GRS Enqueue System data section
- Contains data for GRS ENQ SCOPE=SYSTEM requests per address space.
This section is mapped by GRS enqueue data.
- GRS Enqueue Systems data section
- Contains data for GRS ENQ SCOPE=SYSTEMS requests per address space.
This section is mapped by GRS enqueue data.
- GRS QScan Statistics data section
- Contains data about GQSCAN and ISGQUERY REQINFO=QSCAN requests
per address space (see GRS QScan statistics data section).
Each subtype contains a header section followed by the RMF Product section.
Macro to Symbolically Address Record Type 72: The SMF record
mapping macro for all records produced by RMF is
ERBSMFR. Its format is ERBSMFR (n1,n2,...)
where n1,n2, ... are the SMF
record types you want to map. Note that the parentheses are required
only when two or more record types are specified. The mapping macro
resides in SYS1.MACLIB.
For information on using RMF,
see z/OS RMF User's Guide.
For more information on Monitor I, II, and III, see z/OS RMF Report Analysis.
For information on the MVS™ workload
manager, see z/OS MVS Planning: Workload Management and z/OS MVS Programming: Workload Management Services.