Report control statements


All control statements are optional.

If specified, each statement must begin in column 1. The following table contains descriptions for each control statement.

Statement

Description

FROM DATE

Starting date of the data to be included in the report, in mm/dd/yyyy format

If the statement is omitted, no data is rejected as too old.

Note

If you specify a date in the old format (mm/dd/yy), yy is interpreted as 19yy.

TO DATE

Ending date of the data to be included in the report, in mm/dd/yyyy format

If the statement is omitted, no data is rejected as too new.

Note

If you specify a date in the old format (mm/dd/yy), yy is interpreted as 19yy.

FROM TIME

Starting time of the data to be included in the report, in hh:mm:ss format

If the statement is omitted, no data is rejected as too early

TO TIME

Ending time of the data to be included in the report, in hh:mm:ss format

If the statement is omitted, no data is rejected as too late.

SORTWK

Number of sort work areas to be used

Valid values are 1 to 8. If a value greater than 1 is specified, a corresponding number of DD or DLBL statements must appear in the JCL.

INPUT

Type of input data set to be used and can be specified as one of the following values:

  • VSAM (VSAM data set—the default)
  • TAPE (sequential tape or disk file)

TYPE

Type of report to be generated, which can be any one of the following values:

  • SUMMARY reports three lines of transaction execution data for each transaction or program by calendar date. This value is the default. A sample of this type of report is in the Transaction Resource Tracking and Analysis report.
  • DETAIL reports three lines of transaction execution data for each transaction or program.
  • SERVICE specifies DETAIL information, but only for transactions or programs that did not meet their service levels.

TABLE

Module name of the customized CMRRAPM table

The default is CMRRAPM.



 

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