Supervisor Scope Activities

Edit online

This reference lists and describes Supervisor Scope Activities.

Supervisor-Resource-1, 2, or 3
Supervisor Resource anomalies identify potential z/OS® internal resource concerns. You have limited ability to impact these anomalies, so their attributes are masked.
In the Inspector Web UI, Supervisor Resource Anomaly Signatures that are prefixed with (RR) are marked Resilience Risk. You can report the Anomaly Signatures to IBM® by including each worst (RR) Anomaly Signature instance (R1). To include each worst (RR) Anomaly Signature instance (R1), check the checkbox in the Date Time column, and then click the button . This opens a Resilience Risk Case and attaches the package.
Checkbox for packaging SMF files

When you perform analysis in the Navigator Web UI, if a Supervisor Resource x anomaly with a peer jobname is concerning, perform Inspection with Recent set before the anomaly. If Supervisor Resource x with that peer jobname became an Anomaly Signature that is marked Resilience Risk (RR), report it to IBM. For more information about the process, see the process in the Inspector UI.

CPU Time
This simple activity in the Detail group tracks the amount of CPU time that is consumed by a job or workload component at each point in time. This CPU time is tracked independently for CPs and zIIPs.
  • The job size workload component attribute assigned to a job is directly correlated to the amount of CP or zIIP CPU Time that job consumed for that point in time.
  • The size of a job may change at different points in time due to changes in its CPU consumption. For example, a job may change its workload component attribute from Small to Tiny because it used less CPU.
For the descriptions for the hover text on the graph, see Table 1.
CPU Time Per Dispatch
The periodic running of work units by the OS on a CPU, for example, tasks within a job, is called a dispatch. This compound activity in the Detail group tracks the average CPU Time Per Dispatch, which is calculated by dividing the CPU Time of a work unit by the number of dispatches that occurred over that same period at each point in time. This CPU time is tracked independently for CPs and zIIPs.
  • When no software changes have been applied, this value may transiently change due to the batching of items assigned to a work unit, for example, each dispatch has more items to process.
  • Another cause for changes in this value is that when software changes are made, the CPU demands of a task increase or decrease.
  • Significant (transient) decreases in processor execution efficiency due to increased work unit parallelism and / or CPU demand. This might be another cause for changes in values for this activity.
For the descriptions for the hover text on the graph, see Table 2.
Cycles Per Instruction (CPI)
CPI is used to define the execution efficiency of the processor for a job or workload component. Increasing the execution efficiency or lowering the CPI generally lowers the cost to get work done. This compound activity in the Detail group tracks the CPI of workload component at each point in time.
  • Because increased work unit parallelism and/or CPU demand within the OS image, which is caused by work arrival pattern increases, the CPI may transiently change over time.
  • Broad CPI changes may also occur at the time of CPC hardware upgrades.
For the descriptions for the hover text on the graph, see Table 3.
Dispatches
The periodic running of work units by the OS on a CPU, for example, tasks within a job, is called a dispatch. This simple activity in the Detail group tracks the number of dispatches of a workload component at each point in time.
For the descriptions for the hover text on the graph, see Table 4.
Input/Output Requests (I/Os)
This simple activity in the Global group tracks the global number of I/O requests at each point in time.
Jobs Contributing
This simple activity in the Detail group tracks the number of Jobs that contributed to a workload component at each point in time.
  • This activity is included in graph hover text for many activities.
  • Changes in the number of jobs contributing to a workload component may impact the graphed values of the current activity at the point of change.
For the descriptions for the hover text on the graph, see Table 5.
Continuous CPU Demand
This compound activity in the Global group tracks the average time a CPU works before entering a no-work wait.