Less frequently used control statements

REPLACE={NO | YES}

REPLACE specifies whether data collected during the execution of the job replaces any data from previous executions that have the same workloads

This control statement applies to VSAM data sets only. You must use REPLACE to re-create workloads from detail records that have been previously processed. By default, the data is combined with existing data.

FILES={TIME | SUMMARY | COUNT}

FILES specifies the summarization option for the file entries in the records

If you specify FILES prior to the first WORKLOAD control statement, it defines the default type of summarization for all workloads, as follows:

• TIME (summarizes records by file entries, and the 255 files with the longest elapsed I/O time are written to the summarized file) TIME is the default.
• SUMMARY (summarizes all entries, and only the first 20 entries are written to the summarized file)
• COUNT (summarizes the file entries, and the 20 files with the largest number of I/Os are written to the summarized file).

DETAIL={NO | YES}

DETAIL specifies whether the summarization utility treats files as individual entities or as a single entity for each file type. If you specify DETAIL prior to the first WORKLOAD control statement, it defines the default value for all workloads.

• NO summarizes files entries by a common resource, such as CICS, Software AG ADABAS, DBCTL, DB2, and so forth (the default).
• YES specifies that you want each file entry processed separately.

ZERODATA={NO | YES}

ZERODATA specifies whether intervals are written to the summarized file when no tasks are executed for a given workload; for example, when CICS is not active, no tasks are executed.

If you specify ZERODATA before the first WORKLOAD control statement, it defines the default value for all workloads.

Values are as follows:

• NO specifies that the utility does not write intervals with zero tasks to the summarized file (the default).
• YES specifies that the utility writes intervals with zero tasks to the summarized file.

FROM DATE=mm/dd/yyyy

FROM DATE specifies the starting date of the selected records.

You can specify the starting date using a relative format that is an offset from the current date. For example, to start the selected records with yesterday’s date, specify

FROM DATE=*-1

If you specify FROM DATE before the first WORKLOAD control statement, it defines the default starting date for all workloads.

TO DATE=mm/dd/yyyy

TO DATE specifies the ending date of the selected records.

You can specify the ending date using a relative format that is an offset from the current date. For example, to end the selected records with yesterday’s date, specify:

If you specify TO DATE before the first WORKLOAD statement, the utility provides the default ending date for all workloads at the workload level.

FROM TIME=hh:mm:ss

FROM TIME specifies the starting time of the selected records. The format is hh:mm:ss.

If you specify FROM TIME before the first WORKLOAD control statement, it defines the default starting time for all workloads.

TO TIME=hh:mm:ss

TO TIME specifies the ending time for selecting records. The format is hh:mm:ss.

If you specify TO TIME before the first WORKLOAD control statement, it defines the default ending time for all workloads.

START TIME=hh:mm:ss

START TIME specifies the starting time for the selection interval. You can use this time to specify a period, such as the prime shift for a given workload.

STOP TIME=hh:mm:ss

STOP TIME specifies the ending time for the selection interval. STOP TIME can be used with TO DATE to specify an ending date and time.

The following example shows START TIME, STOP TIME, FROM TIME, and TO TIME control statements together in a job stream.

In this example, the default date and time ranges for the selected records are from noon five days ago through yesterday at noon.

Workload TEST1 uses records that are collected between 8:00 A.M. and 5:00 P.M. On the first day, records are collected from 12:00 P.M. to 5:00 P.M. On the last day, records are collected from 8:00 A.M. to 12:00 P.M.

Workload TEST2 collects records from noon four days ago through the following day at noon.

MINRESP=nnnnn.nnn

MINRESP sets a minimum response time threshold of a transaction record in seconds. Records with transaction response times that exceed the minimum threshold are included in the summarization workload. Records with response times less than the threshold are excluded.

MAXRESP=nnnnn.nnn

MAXRESP sets a maximum response time threshold of a transaction record in seconds. Records with response times less than the maximum threshold are included in the summarization workload. Records that exceed the maximum response time are excluded.

The MINRESP and MAXRESP control statements are often used together to filter transaction records by response times. You can create summary workloads that contain only those transactions with response times that fall within the interval set by the two control statements.

MINCPU=nnnnn.nnn

MINCPU sets a minimum CPU usage threshold of a transaction record in seconds. Records with CPU usage that exceed the minimum threshold are included in the summarization workload. Records with CPU usage less than the threshold are excluded.

MAXCPU=nnnnn.nnn

MAXCPU sets a maximum CPU usage threshold of a transaction record in seconds. Records with CPU usage less than the maximum threshold are included in the summarization workload. Records that exceed the maximum threshold are excluded.

The MINCPU and MAXCPU control statements can be used together to filter transaction records by CPU usage. You can create summary workloads that contain only those transactions with CPU usage that falls within the interval set by the two control statements.