Default language.

PERFSUM

The PERFSUM control statement requests the Performance Summary Report.

PERFSUM
[BOTNECKS=([ENQUEUE={10|nn}][,CHANNEL={50|nn}]
    [,OVERUTIL={95|nn}][,UNDERUTL={20|nn}]
    [,PAGING={50|nn}][,TSO={15|nn}]
    [,SUPERVSR={50|nn}][,AUXSTORE={90|nn})]

The PERFSUM statement uses data collected by the following Extractor control statements. See a discussion of these statements in the section that covers 'Extractor control statements.'

  • ASMDATA
  • CPU
  • CHANNEL
  • DEVICE
  • ENQUEUE
  • EXTSUM
  • PAGING
  • TSODATA
  • WORKLOAD

Related topics

ASMDATA
CHANNEL-Extractor-control-statements
CPU
ENQUEUE
EXTSUM
PAGING
WORKLOAD
Performance-Summary-Report
PERFORM
Report-control-statements-Analyzer

Parameters

The parameters for the PERFSUM control statement are as follows:

BOTNECKS=

specifies the major parameter under which all of the following minor parameters fall

This parameter must be coded. Parentheses must enclose the minor parameters if more than one is coded; for example:

BOTNECKS=(CHANNEL=60,TSO=2)

ENQUEUE=

specifies the percentage of total time that an excessive ENQUEUE conflict existed; the default is 10%

CHANNEL=

specifies the percentage of overused channel path busy time; the default is 50%

OVERUTIL=

specifies the percentage of overused CPU busy time; the default is 95%

UNDERUTL=

specifies the percentage of underused CPU busy time; the default is 20%

PAGING=

specifies a value for average pages per second that would be considered too high; the default is 50 pages per second

TSO=

specifies an average TSO response time that would be considered too high; the default is 15 seconds

SUPERVSR=

specifies a percentage of CPU busy time spent excessively in supervisor state; the default is 50%

AUXSTORE=

specifies the percentage of overused auxiliary storage slots; the default is 90%

Important

  • If the PERFORM control statement is not specified after the PERFSUM control statement, the Analyzer looks for PERFORM data written at Extractor initialization.
  • If the PERFORM parameter was specified on the Extractor EXTSUM control statement, the data is only available to the Analyzer if the records, written at Extractor initialization, are included in the input data. It is not necessary to include the period of these records in the DATETIME or SHIFT ranges.

Example

This example produces a Performance Summary Report designating bottleneck tolerance thresholds: the percentage of time the CPU is over 98% busy; the percentage of channel busy time over 35%; average pages per second over 20; and TSO response time in excess of 6 seconds.

PERFSUM  BOTNECKS=(OVERUTIL=98,CHANNEL=35,PAGING=20,TSO=6)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*