The workload report

To create a workload report, issue a REPORT WORKLOAD command. For the syntax of this command, see page REPORT WORKLOAD. The report contains information the workload that is currently being observed. The reported information indicates:

• The number of systems for which the workload can be observed.
• For each system that is observed:
  • The name of the system, the name of the sysplex the system belongs to, and the name of the CPC the system is running on.
  • For each WLM service class period that is observed on the system:
    • The name and number of a service class period, for example, SAMPSC.1, followed by the provisioning performance index limit (PL), the provisioning performance index limit duration (PD), the deprovisioning performance index limit (DL), the deprovisioning performance index limit duration (DD), and the scope for the performance index (S).
    • The last measured performance index and the time of this measurement. A dash (-) is displayed whenever the performance index is not available at the time of measurement; for example, this situation can occur when the workload that is running in the observed service class has been displaced. To show how long the performance index has been at this level, the line also indicates the last time the performance index crossed the provisioning or deprovisioning performance index limit. Both times are shown in UTC.
    • If a detailed workload report is issued (type=detailed), it also lists the types of additional capacity that are needed for a service class that is suffering, or, optionally, the reason why additional capacity is not needed by a suffering service class.

An example of a workload report is:

CPO1047I Workload report generated at 12/22/2012 08:55:10
Workload is analyzed for 1 system(s)
Workload for system SYSTEM1 of sysplex SYSPLEX on CPC SAMPCPC
 SAMPSC.1 PL/PD/DL/DD/S 1.4 10 1.2 10 Sysplex
  PI from 12/22/2012 08:54 is 1.6. Last limit crossing was 12/22/2012 08:45
   Demand for additional logical zIIPs not recognized
    Lack of spare logical zIIPs
   Demand for additional physical zAAPs not recognized
    Shared logical zAAPs not available on LPAR
   Demand for additional logical CPs recognized
   Demand for capacity level increase only recognized.
   Demand for additional physical CPs not recognized
    Amount of logical online CPs outnumbers amount of physical CPs

If management with moving average PI is enabled, the workload report lists the user-settings that are being used for the moving average PI calculation, such as weight and capping. The report also lists the PI as it has been reported by WLM for each observed WLM service class period, as well as the alternate moving average PI that is calculated by Capacity Provisioning.

An example for this kind of workload report is:

CPO1047I Workload report generated at 12/22/2012 08:55:11
Workload is analyzed for 1 system(s)
average PI management enabled: weight 57%, capping PI 2.79
Workload for system SYSTEM1 of sysplex SYSPLEX on CPC SAMPCPC
 SAMPSC.1 PL/PD/DL/DD/S 1.4 10 1.2 10 Sysplex
  average PI from 12/22/2012 08:54 is 1.46. Last limit crossing was 12/22/2012 08:47
  PI from 12/22/2012 08:54 is 1.6. Last limit crossing was 12/22/2012 08:45

For setting the moving average weight, see key SystemObservation.MovingAveragePiWeight in Table 17.

For setting the moving average capping, see key SystemObservation.MovingAveragePiCapping in Table 17.