REPORT WORKLOAD

Use the REPORT WORKLOAD command to display the WLM service class periods that are currently being monitored on the observed systems.

For information about what is contained in the report, see page The workload report.

Syntax

Read syntax diagramSkip visual syntax diagram                         .-TYPE=NORMAL------.                          .-DEST=*----.
>>-+-REPORT--WORKLOAD-+--+------------------+--+--------------------+--+-----------+-><
   '-R--W-------------'  +-TYPE=DETAILED----+  '-PLEX=name SYS=name-'  '-DEST=file-'
                         +-TYPE=WITHPIONLY--+
                         '-TYPE=ABOVEPLONLY-'

Parameters

The command has the following parameters:

TYPE=type
The type of report to display. The following types are supported:
NORMAL
Displays a short workload report
DETAILED
Displays a workload report that includes detailed information about WLM service class periods that are suffering. For each service class period, the report lists which types of additional capacity are needed, or why additional capacity is not needed.
WITHPIONLY
Displays a detailed workload report that lists workloads with a recent PI measurement only.
ABOVEPLONLY
Displays a detailed workload report that lists only workloads with a PI that is above the corresponding provisioning limit (PL), as specified in the provisioning policy.
PLEX=name
The name of the sysplex to which the specified system belongs.
SYS=name
The name of the system whose workload you want to list exclusively. The specified system must be part of the active domain configuration and it must also be currently observed.
DEST=
The destination of the workload report. The following destinations are supported:
*
(Default) specifies the report should be written to the console issuing the command.
file
Specifies a file where the information is to be stored. If the name includes lowercase characters this parameter must be enclosed in single quotation marks ('). The file must be in the hierarchical file system. You can specify either an absolute, path or a relative path to the file. If this is not absolute the path is relative to the home directory of the user who is running the Provisioning Manager. Make sure that there is sufficient space in the selected location. The Provisioning Manager user must be authorized to write to this location.