Address Space Delay Summary History attributes

The historical address space common storage attribute group provides historical address space common storage usage information for all address spaces

ASID The address space ID of the job (hexadecimal format). The address space id of a Job, TSO Userid, started task or UNIX System Services address space.

Capping Wait Percentage (RMF metric) Percentage of time delayed because of capping.

The job is delayed due to WLM resource capping for one of the following reasons:

  • The resource group for which the job is running, has used up its CPU service specified in the WLM policy.
  • The work for which the job is running is overachieving its goal. So this work may be capped in order to divert its resources to run discretionary work

Common Paging Wait Percentage (RMF metric) Percentage of time waiting for common storage.

The percentage of time that common (CSA or LPA) storage paging contributes to the delay of the job from the time of the page fault until I/O is completed. The shared storage paging is also included.

GCP 1st Impactor Job Name (RMF metric) The primary impactor on the General Capacity Processor (GCP) resource of the current job.

The name of a job contributing the most delay to the job waiting to use the processor. The name *ENCLAVE in this field means that one or more enclaves are active on the processor. The percentage shown for enclaves is the sum of all enclave using samples found while the reported job was delayed.
% = (# Holding Samples / # Samples) * 100
Holding samples: The number of samples when the job was using the processor and delaying the other job (indicated in the Jobname field).

GCP 1st Impactor Percentage (RMF metric) The percentage impact of the primary impactor on the General Capacity Processor (GCP) resource of the current job.

The percentage of delay caused by the primary impacting job to the job waiting to use the processor.

GCP 2nd Impactor Job Name (RMF metric) The secondary impactor on the General Capacity Processor (GCP) resource of the current job.

The name of a job contributing the second most delay to the job waiting to use the processor. The name *ENCLAVE in this field means that one or more enclaves are active on the processor. The percentage shown for enclaves is the sum of all enclave using samples found while the reported job was delayed.
% = (# Holding Samples / # Samples) * 100
Holding samples: The number of samples when the job was using the processor and delaying the other job (indicated in the Jobname field).

GCP 2nd Impactor Percentage (RMF metric) The percentage impact of the secondary impactor on the General Capacity Processor (GCP) resource of the current job.

The percentage of delay caused by the second most impacting job to the job waiting to use the processor.

GCP 3rd Impactor Job Name (RMF metric) The tertiary impactor on the General Capacity Processor (GCP) resource of the current job.

The name of a job contributing the third most delay to the job waiting to use the processor. The name *ENCLAVE in this field means that one or more enclaves are active on the processor. The percentage shown for enclaves is the sum of all enclave using samples found while the reported job was delayed.
% = (# Holding Samples / # Samples) * 100
Holding samples: The number of samples when the job was using the processor and delaying the other job (indicated in the Jobname field).

GCP 3rd Impactor Percentage (RMF metric) The percentage impact of the tertiary impactor on the General Capacity Processor (GCP) resource of the current job.

GCP Using Percentage (RMF metric) The percentage of time using general-purpose processors (CPs)

The percentage of time when the job is receiving service from the general (CP) processor type.
Using % = (# Using Samples / # Samples) * 100
Using Samples: The number of samples when the job was found using the processor. If the processor running Monitor III has other ready work to do (any ready SRB, interrupted ready task, asynchronous exit routine, or TCB is on the dispatching queue), then it looks for the first address space having a unit of work on the dispatching queue that is not already using another processor. Then the number of samples is incremented by one for the address space having the first dispatchable unit of work according to the dispatcher sequence search order. The processor running Monitor III is not counted as a processor in use if there is no other ready work to do.

The percentage of delay caused by the third most impacting job to the job waiting to use the processor.

GCP Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed waiting for a GCP processor.

Delay percentage that the waiting job (address space) is experiencing because of contention for the GCP processor during the report interval.
Delay % = (# Delay Samples / # Samples) * 100
Delay samples: The single state count of samples being delayed by the processor. RMF increments this count only once for each sample when one or more units of work (TCBs, SRBs, interrupted ready task or asynchronous exit) associated with the address space are delayed for the processor.

Hiperspace Paging Wait Percentage (RMF metric) Percentage of time the job is waiting for Hiperspace Page.

Paging delays from standard hiperspaces, except ESO hiperspaces.

This is a single state sum, which means that whenever several of the delays (VIO, XMEM, or Hiperspace) are detected in the same cycle, they are counted as one occurrence of Other Page

Idle Wait Percentage (RMF metric) Percentage of address space elapsed time that it was idle. Jobs in terminal wait, timer wait, or waiting for job selection by the Job Entry Subsystem (JES) are in an idling state if they are not using the processor or devices and are not delayed for any monitored reason. Jobs classified as in terminal wait meet all of the following conditions:

  • They are not found using any monitored resource
  • They are not found delayed for any monitored reason
  • They are swapped out
  • They are in terminal wait
  • They are waiting for a user ready indication before being swapped in

Jobs classified as in timer wait meet all of the following conditions:

  • They are not using or delayed for a monitored resource
  • Their address space is waiting for a timer
The idling percentage of an address space can vary 0 - 100%, where 0% indicates that the user is not idling during the report interval, and 100% represents a job that is idle at every sample. The idling percentage for an address space during a refresh period is calculated as follows:
Idle % = (# Idle Samples / # Samples) * 100
Idle samples: The number of samples that show the job in an idle state.

Job Name (RMF metric) The name of the job, job group or enclave.

The enclave names, starting with the letters ENC, and belonging to class E, are created dynamically by RMF. You cannot use the names to track a particular enclave through different time ranges. However, the enclave token is used when combining multiple set-of-samples, so that data is combined only for the same individual enclaves, thus providing consistent data. Unavailable is shown if the value does not apply to enclaves.

Managed System A z/OS operating system in your enterprise that is being monitored by an IBM® Z OMEGAMON AI for z/OS agent. Valid value is a character string with a maximum length of 32 bytes.

Operator Mount Wait Percentage (RMF metric) Percentage time waiting for an operator mount request.

Operator Reply Wait Percentage (RMF metric) Percentage of time waiting for an operator message reply.

Operator Quiesce Wait Percentage (RMF metric) Percentage of time waiting for an operator quiesce operation.

Quiesce means that the operator has quiesced the address space. A quiesced address space can show unexpected data:

  • A swappable address space will be swapped out, thus it can be OUTR and show storage delays.
  • A non-swappable address space will get lowest priority, thus it can show CPU delay, paging delay, or other delays, and even some using percentage from time to time depending on the load on the system.

Other Paging Wait Percentage (RMF metric) Percentage of time the job is waiting for VIO, XMEM or Hiperspace Page.

Out and Ready Wait Percentage (RMF metric) Percentage of time the job is swapped out and ready.

The percentage of time that being swapped out and ready contributes to the delay of the job.

Private Paging Wait Percentage (RMF metric) Percentage of time waiting for private page (includes shared paging).

The percentage of time that local (private) storage paging contributes to the delay of the job from the time of the page fault until I/O is completed. The shared storage paging is also included

Recording End Time Time at the end of the RMF reporting interval for the current row of near-term historical data. The valid format is yy/mm/dd hh:mm:ss.

Recording Start Time Time at the start of the RMF reporting interval for the current row of near-term historical data. The valid format is yy/mm/dd hh:mm:ss.

RMF Status Status indications for availability of RMF and lock data.

Sample Period Sample period in seconds.

Service Class (RMF metric) The service class name. Valid value is a string, with a maximum of 8 characters. This field displays unavailable if the system is in compatibility mode. If a job changes its service class during the report interval, RMF displays eight asterisks (********) instead of the service class name. If the service class is not available, RMF displays eight dashes (--------).

Service Class Alternate (RMF metric) This is the same as Service Class and is used for navigation from certain workspaces. Valid value is a string, with a maximum of 8 characters. This field displays unavailable if the system is in compatibility mode. If a job changes its service class during the report interval, RMF displays eight asterisks (********) instead of the service class name. If the service class is not available, RMF displays eight dashes (--------).

SMF ID SMF ID as defined in the IEASYM or IEASYS PARMLIB members.

Swap Paging Wait Percentage (RMF metric) Percentage of time waiting for swap paging.

The percentage of time that swapping contributes to the delay of the job from the time of swap initiation until the last swap page I/O is completed.

Total CPU Using Percentage (RMF metric) The percentage of time using CPU (All processor types).

When calculating the Using percentage, RMF counts an address space as using a resource even if the address space is also delayed for the identical resource (single state case). For example, if a job has four ready tasks in its address space, and one task is using the processor while three tasks are simultaneously delayed for the processor, RMF considers this address space to have a Using count of one and a Delay count of one
Using % = (Using Samples / # Samples) * 100

Total CPU Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed for processors (GCPs and zIIPs).

The job has ready work on the dispatching queue, but it is not being dispatched.

The job is waiting for a COMM, LOCL, SWAP, XMEM, HIPR or VIO page, or is on the out/ready queue.

Total Enqueue Wait Percentage (RMF metric) Total percentage of time waiting for enqueues.

The job is waiting to use an enqueued (reserved) resource.

Total Device Using Percentage (RMF metric) Percentage of time using a device (all DASD and Tape).

The percentage of time when the job is transferring data between DASD or tape and central storage. (Not just the volumes listed under the VOLSER columns on the report.)

Total Device Wait Percentage (RMF metric) The percentage of time waiting for a device (All DASD and Tape).

1st Device Wait Percentage (RMF metric) The largest percentage of delay caused because the job was waiting to use the named volume.

1st Device Volume Serial (RMF metric) The serial number of the DASD or tape contributing the most to the job delay.

2nd Device Wait Percentage (RMF metric) The second largest percentage of delay caused because the job was waiting to use the named volume.

2nd Device Volume Serial (RMF metric) The serial number of the DASD or tape contributing second most to the job delay.

3rd Device Wait Percentage (RMF metric) The third largest percentage of delay caused because the job was waiting to use the named volume.

3rd Device Volume Serial (RMF metric) The serial number of the DASD or tape contributing third most to the job delay.

4th Device Wait Percentage (RMF metric) The fourth largest percentage of delay caused because the job was waiting to use the named volume.

4th Device Volume Serial (RMF metric) The serial number of the DASD or tape contributing fourth most to the job delay.

Total HSM Wait Percentage (RMF metric) Percentage of time waiting for a HSM Request

1st HSM Wait Percentage (RMF metric) Percentage of time waiting for the 1st HSM request.

1st HSM Wait Reason (RMF metric) The reason the address space was delayed waiting for the 1st HSM request. Valid values are:

  • Dataset recall from AUX storage
  • Dataset being recovered
  • Dataset being migrated
  • Dataset being backed up
  • HSM Function Code 8
    • Control dataset record being read
    • JES3 C/I locate being done
  • Dataset being deleted

2nd HSM Wait Percentage (RMF metric) Percentage of time waiting for the 2nd HSM request.

2nd HSM Wait Reason (RMF metric) The reason the address space was delayed waiting for the 2nd HSM request. Valid values are:

  • Dataset recall from AUX storage
  • Dataset being recovered
  • Dataset being migrated
  • Dataset being backed up
  • HSM Function Code 8
    • Control dataset record being read
    • JES3 C/I locate being done
  • Dataset being deleted

Total JES Wait Percentage (RMF metric) Percentage of time waiting for a Job Entry Subsystem (JES) request

1st JES Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed waiting for the 1st JES request. Valid value is a 4-byte integer.

1st JES Wait Reason (RMF metric) The reason the address space was delayed waiting for the 1st JES request. Valid values are:

  • Processing TSO OUTPUT command
  • Wait for JES to cancel job
  • Wait for job status information
  • Wait for WTO or WTOR request
  • Wait for job termination
  • Wait for JES to restart a job
  • JES Function Code 23
    • Wait for dynalloc via SSOBDYCD
    • Wait for SETUP request
  • Wait for change DD name
  • Wait for change ENQ use attrib
  • Processing notify user
  • Wait for JDS access
  • JES Function Code 138
    • Validating SYSOUT destination
    • Wait for JES to cancel a job
    • Wait for job status information
  • Wait for ENDREQ
  • Processing TSO OUTPUT command
  • Dynalloc data set to JES3
  • Change JES3 DD via dynalloc
  • Wait for FSS request
  • Wait for CI driver
  • Wait for SYSOUT API request
  • Processing SSI Extended Status
  • Wait for TCPIP NJE global svcs
  • Wait for job class information
  • Wait for initiator information
  • Wait for NJE node information
  • Wait for spool partition info
  • Wait for JESPLEX information
  • Wait for SJF services
  • Wait for JES device information
  • Wait for SPOOL space

2nd JES Wait Reason (RMF metric) The reason the address space was delayed waiting for the 2nd JES request. Valid values are:

  • Processing TSO OUTPUT command
  • Wait for JES to cancel job
  • Wait for job status information
  • Wait for WTO or WTOR request
  • Wait for job termination
  • Wait for JES to restart a job
  • JES Function Code 23
    • Wait for dynalloc via SSOBDYCD
    • Wait for SETUP request
  • Wait for change DD name
  • Wait for change ENQ use attrib
  • Processing notify user
  • Wait for JDS access
  • JES Function Code 138
    • Validating SYSOUT destination
    • Wait for JES to cancel a job
    • Wait for job status information
  • Wait for ENDREQ
  • Processing TSO OUTPUT command
  • Dynalloc data set to JES3
  • Change JES3 DD via dynalloc
  • Wait for FSS request
  • Wait for CI driver
  • Wait for SYSOUT API request
  • Processing SSI Extended Status
  • Wait for TCPIP NJE global svcs
  • Wait for job class information
  • Wait for initiator information
  • Wait for NJE node information
  • Wait for spool partition info
  • Wait for JESPLEX information
  • Wait for SJF services
  • Wait for JES device information
  • Wait for SPOOL space

2nd JES Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed waiting for the 2nd JES request.

Total Operator Wait Percentage (RMF metric) Percentage of time waiting for an Operator Request (Mount, Message Reply, Quiesce).

The job is delayed by a message or a mount request or a quiesce. Quiesce means that the operator has quiesced the address space. A quiesced address space can show unexpected data:

  • A swappable address space will be swapped out, thus it can be Out Ready and show storage delays.
  • A non-swappable address space will get lowest priority, thus it can show CPU delay, paging delay, or other delays, and even some using percentage from time to time depending on the load on the system.

Total Storage Wait Percentage (RMF metric) Percentage of time waiting for a storage request ( all types).

The job is waiting for a COMM, LOCL, SWAP, XMEM, HIPR or VIO page, or is on the out/ready queue.

Total Subsystem Wait Percentage (RMF metric) Percentage of time waiting for a subsystem request (JES, HSM or XCF).

Total Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed waiting for processors and devices.

The delay of an address space represents a job that needs one or more resources but that must wait because it is contending for the resource(s) with other users in the system.
Delay % = (# Delay Samples / # Samples) * 100
When calculating Delay, Monitor III counts an address space as delayed for a resource if at least one ready user (unit of work) is waiting for a device or processor. In the case of single state sampling, if a job has more than one ready tasks simultaneously delayed for the processor, Monitor III considers this address space to have a delay count of one.

Total XCF Wait Percentage (RMF metric) Percentage of time waiting for a XCF request.

Unknown Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed for an unknown reason.

RMF considers jobs that are not delayed for a monitored resource, not using a monitored resource, or not in an idling state to be in an unknown state. Examples of address spaces in an unknown state are:

  • Idle address spaces that use a non-monitored mechanism for determining when they are active. Most system tasks (STC) show up as unknown when they are idle.
  • Address spaces waiting for devices other than DASD or tape.

The unknown state percentage for an address space can vary from 0 to 100%, where 0% indicates that the state was always known during the report interval and 100% represents a job in an unknown state throughout the report interval.

Velocity Percentage (RMF metric) The address space velocity, that is, the percentage of time the address space obtained resources when they were needed.

A value from 0 to 100% indicates the velocity within the report interval. A low velocity value indicates that a job has few of the resources it needs and is contending with other jobs for system resources. A high velocity value indicates that a job has all the resources it needs to execute, and that it is moving through the system at a relatively high speed.
Velocity = ( # Using Samples / (# Using Samples + # Delay Samples)) * 100

VIO Paging Wait Percentage (RMF metric) Percentage of time waiting for VIO Paging.

The percentage of time that VIO paging contributes to the delay of the job from the time of the page fault until I/O is completed.

XMEM Paging Wait Percentage (RMF metric) Percentage of time the job is waiting for cross-memory page.

The percentage of time that paging delays from cross memory address spaces contributes to the delay of the job.

zCBP 1st Impactor Job Name Primary impactor on current job zCBP resource

zCBP 1st Impactor Percentage Percentage impact of primary impactor on current job zCBP resource

zCBP 2nd Impactor Job Name Secondary impactor on current job zCBP resource.

zCBP 2nd Impactor Percentage Percentage impact of secondary impactor on current job zCBP resource.

zCBP 3rd Impactor Job Name Tertiary impactor on current job zCBP resource.

zCBP 3rd Impactor Percentage Percentage impact of tertiary impactor on current job zCBP resource.

zCBP On CP Using Percentage Percentage zCBP on CP Using.

zCBP Using Percentage Percentage Using zCBP Processors.

zCBP Wait Percentage Percentage of Waiting for a zCBP Processor.

zIIP On CP Using Percentage (RMF metric) Percentage of CPU time consumed on general processors by work that was eligible for a zAIIP.

zIIP Using Percentage (RMF metric) The percentage of time using zIIPs.

The percentage of time when the job is receiving service from the zIIP processor type 
Using % = (# Using Samples / # Samples) * 100
Using samples: The number of samples when the job was found using the processor. If the processor running Monitor III has other ready work to do (any ready SRB, interrupted ready task, asynchronous exit routine, or TCB is on the dispatching queue), then it looks for the first address space having a unit of work on the dispatching queue that is not already using another processor. Then the number of samples is incremented by one for the address space having the first dispatchable unit of work according to the dispatcher sequence search order. The processor running Monitor III is not counted as a processor in use if there is no other ready work to do.

zIIP Wait Percentage (RMF metric) Percentage of address space elapsed time that it was delayed waiting for a zIIP processor.

Delay percentage that the waiting job (address space) is experiencing because of contention for the zIIP processor during the report interval.
Delay % = (# Delay Samples / # Samples) * 100
Delay samples: The single state count of samples being delayed by the processor. RMF increments this count only once for each sample when one or more units of work (TCBs, SRBs, interrupted ready task or asynchronous exit) associated with the address space are delayed for the processor.

zIIP 1st Impactor Job Name (RMF metric) The primary impactor on the System z Integrated Information Processor (zIIP) resource of the current job.

The name of a job contributing the most delay to the job waiting to use the processor. The name *ENCLAVE in this field means that one or more enclaves are active on the processor. The percentage shown for enclaves is the sum of all enclave using samples found while the reported job was delayed.
% = (# Holding Samples / # Samples) * 100
Holding samples: The number of samples when the job was using the processor and delaying the other job (indicated in the Jobname field).

zIIP 1st Impactor Percentage (RMF metric) The percentage impact of the primary impactor on the System z Integrated Information Processor (zIIP) resource of the current job.

The percentage of delay caused by the primary impacting job to the job waiting to use the processor.

zIIP 2nd Impactor Job Name (RMF metric) The secondary impactor on the System z Integrated Information Processor (zIIP) resource of the current job.

The name of a job contributing the second most delay to the job waiting to use the processor. The name *ENCLAVE in this field means that one or more enclaves are active on the processor. The percentage shown for enclaves is the sum of all enclave using samples found while the reported job was delayed.
% = (# Holding Samples / # Samples) * 100
Holding samples: The number of samples when the job was using the processor and delaying the other job (indicated in the Jobname field).

zIIP 2nd Impactor Percentage (RMF metric) The percentage impact of the secondary impactor on the System z Integrated Information Processor (zIIP) resource of the current job.

The percentage of delay caused by the second most impacting job to the job waiting to use the processor.

zIIP 3rd Impactor Job Name (RMF metric) The tertiary impactor on the System z Integrated Information Processor (zIIP) resource of the current job.

The name of a job contributing the third most delay to the job waiting to use the processor. The name *ENCLAVE in this field means that one or more enclaves are active on the processor. The percentage shown for enclaves is the sum of all enclave using samples found while the reported job was delayed.
% = (# Holding Samples / # Samples) * 100
Holding samples: The number of samples when the job was using the processor and delaying the other job (indicated in the Jobname field).

zIIP 3rd Impactor Percentage (RMF metric) The percentage impact of the tertiary impactor on the System z Integrated Information Processor (zIIP) resource of the current job.

The percentage of delay caused by the third most impacting job to the job waiting to use the processor.