The Workload Impact Profile

The Workload Impact Profile is another form of overview display in impact analysis that shows a graphic illustration of current contention on your system.

IPRO

Generates the Workload Impact Profile.

Type:

Immediate

Format:

IPRO [IANL                  
               [Workload]
               [GROUP=Groupname]]                  

IPRO does not support the labels S and D, or the suffix PD.

Note the following guidelines for using this command:

• IPRO cannot be used to initiate monitoring. You must first start monitoring the job or group with the IANL command.
• If you do not specify a jobname or group name, IPRO defaults to the last job or group specified with IANL.
• If you do not specify IANL, the operand defaults to the last one issued with IPRO.

The IPRO command remembers its last set of operands, and if it is entered alone, it uses the last operands to construct the profile.

Contending workloads are shown in order of decreasing severity, including self-contention and system contention.

The profile displays only the long-term wait condition figures available with the IANL command, and not the short-term ones, to ensure a statistically significant display.

For terminals with extended color in effect, the Workload Impact Profile appears in the colors set for levels 5, 6, and 7. The graph itself appears in the level 5 color, the impact source labels are in the level 7 color, and the lines pointing from the impact source labels to the graph are in the level 6 color. For information about turning on extended color and setting the color for each level, see The User Profile Facility.

Before you use the Workload Impact Profile, be sure that the impact analysis collectors have been running for several minutes in order to establish a statistically representative sample. For information about how to start the collectors, see Starting and stopping an impact analysis session.

The Workload Impact Profile is most useful when the favored workload is experiencing response time problems. When response time is acceptable, the profile provides a picture of contention that is noncritical, and no tuning is required. If response time worsens due to contention from other workloads, the Workload Impact Profile may also change, indicating a possible cause of the response time problem.