Using the information in the CPU Activity report
LPAR/MVS BUSY TIME PERC values could indicate contention for CPU. To check
this, add the N+1, … N+150 percentages in the
DISTRIBUTION OF IN-READY WORK UNIT
QUEUE (where N is the number of online processors). This sum is the percentage of time when
at least one task could not be dispatched. A value higher than 60% implies contention for CPU.
LPAR/MVS BUSY TIME PERC values can indicate that other bottlenecks in the
system are preventing work from being processed.
OUT READY average value of more than 1 could reflect processor storage
|CPU Activity If multithreading is disabled for the reporting interval (that is, the LOADxx PROCVIEW CPU parameter is in effect), the term logical core refers to a logical processor.
|The hardware description of the CPU.
|Effective processor capacity available to the central processor complex (CPC), measured in MSU/h.
|Reason of the capacity change:
If the mode changed during the reporting interval, an '*' is appended (for example: NO* indicates a switch from YES to NO).
The boost type that was active at the end of the interval:
|The boost class (or period) within which boost was active:
|The logical core identification and the processor type.
|TIME % ONLINE
|The percentage of time the logical core was online.
|TIME % LPAR BUSY
The percentage of the online time that the logical core was dispatched by LPAR.
|TIME % MVS BUSY
|The percentage of the online time that the logical processor was busy.
The MVS view of CPU time is not meaningful if the logical processor is parked during the entire reporting interval. In this case, '----' is shown.
|TIME % PARKED
|The percentage of time that the logical processor was parked. In HiperDispatch mode, processors with a low amount of physical processor share can be parked. That is, they are not dispatched by z/OS and do not attempt to run work. Without HiperDispatch, processors are not parked and '----' is shown.
|MT % PROD
|The percentage of the maximum core capacity that was used in the reporting interval while the
logical core was dispatched to physical hardware.
When MT % PROD equals 100% and the LOADxx PROCVIEW CORE parameter is in effect, all threads on the core are executing work and all core resources are being used. If MT % PROD is less than 100%, the core resources were dispatched to physical hardware but one or more threads on a logical core were in a wait because they had no work to run.
If a core was reconfigured offline/online during the reporting interval, no multithreading core productivity is calculated and '------' is shown. If the LOADxx PROCVIEW CPU parameter is in effect, this field is not displayed.
|MT % UTIL
|The percentage of the maximum core capacity that was used in the reporting interval.
MT % UTIL = MT Core Productivity * TIME % LPAR BUSY
If a core was reconfigured offline/online during the reporting interval, no multithreading core utilization is calculated and '------' is shown. If the LOADxx PROCVIEW CPU parameter is in effect, this field is not displayed.
|LOG PROC SHARE %
|Percentage of the physical processor that the logical processor is entitled to use.
Without HiperDispatch, the processing weight is equally divided between the online logical processors.
In HiperDispatch mode, logical processors have a high, medium or low share of the physical processor. The share percentage is the average value for the reporting interval, whereas HIGH, MED or LOW indicates the HiperDispatch priority at the end of the reporting interval. When the priority changed during the interval, an '*' is appended.
|I/O INTERRUPTS RATE
|The total rate per second that this processor handled I/O interrupts. The rate reflects the
processing for the entire interval. This might include periods of time when the SRM enabled or
disabled this processor for I/O interrupts. The rate includes interrupts handled by the second level
interrupt handler (SLIH), as well as those handled by the Test Pending Interrupt (TPI) instruction.
|I/O INTERRUPTS % VIA TPI
|The percentage of the total interrupts for this processor during the RMF interval that are
handled by the I/O supervisor without re-enabling.
|For the following three TOTAL/AVERAGE values, the logical processors that are parked during the entire interval are not considered in the calculation of the average TIME % MVS BUSY.
|The average or total value for general purpose processors (standard CPs).
|The average value for zAAPs. Only visible if zAAPs are configured online.
|The average value for zIIPs. Only visible if zIIPs are configured online.
|Multi-Threading Analysis: This information is only displayed when the LOADxx PROCVIEW CORE parameter is in effect. Multithreading information is only shown for those processor types for which at least one logical core was configured online for the complete interval.
|Processor type CP, IIP, or AAP.
|The multithreading mode of a processor type designates the number of active threads for each online logical core of this type. If MT MODE is greater than 1, multithreading becomes effective for this processor type.
|Multithreading maximum capacity factor for a processor type. The multithreading maximum
capacity factor represents the ratio of the maximum amount of work that can be accomplished using
all active threads to the amount of work that would have been accomplished within this reporting
interval when multithreading was disabled.
'------' is shown when the multithreading maximum capacity factor cannot be calculated.
|Multithreading capacity factor for a processor type. The multithreading capacity factor
represents the ratio of the amount of work that has been accomplished within this reporting interval
to the amount of work that would have been accomplished with multithreading disabled.
'------' is shown when the multithreading capacity factor cannot be calculated.
|Average thread density for a processor type. This value represents the average number of
active threads for those cores that were dispatched to physical hardware.
'------' is shown when the average thread density cannot be calculated.
|System Address Space and Work Unit Analysis: contains information about the NUMBER OF ADDRESS SPACES categorized by the QUEUE TYPES, in which they have been waiting, and categorized by the ADDRESS SPACE TYPES. Furthermore, the MIN, MAX, and AVG numbers of work units are categorized by the CPU TYPES for which they have been dispatched (that is, for standard CPs, zAAPs and zIIPs). This section also shows how many work units have been waiting in the IN-READY queue (DISTRIBUTION OF IN-READY WORK UNIT QUEUE).
|Shows the number of address spaces that are waiting in the different queues. For each queue
type, the MIN, MAX and AVG numbers of address spaces are displayed.
The following queue types are analyzed:
|ADDRESS SPACE TYPES
|Shows the total number of address spaces detected during the report interval, categorized by
address space types. For each address space type, the MIN, MAX and AVG numbers of active address
spaces are displayed.
The following ADDRESS SPACE TYPES are analyzed:
|DISTRIBUTION OF IN-READY WORK UNIT QUEUE
|The percentaged and graphical distribution of SRM samples when the number of work units on
the IN-READY queue is within a certain range. The correlation is based on N, which is the number of
online logical processors when the sample is taken. In HiperDispatch mode, N is the number of online
logical processors that are not parked.
|NUMBER OF WORK UNITS
by CPU type
|The minimum, maximum and average numbers of running and waiting work units categorized by CPU type (standard CPs, zAAPs and zIIPs).
|Blocked Workload Analysis: provides information about blocked address spaces and enclaves.
|Lists the OPT parameters which define the workload promotion:
If the parameters have been changed during the reporting interval, the values are followed by an '*'.
|WAITERS FOR PROMOTE
|Number of address spaces and enclaves found blocked according to OPT parameter BLWLINTHD: