SELECT control statement


The SELECT control statement specifies the IMS resource data to be plotted and generates the plot (or plots) as requested by the preceding REPORT, XAXIS, and YAXIS control statements.

There is no default for the SELECT control statement. The statement must be entered to generate one or more plots.

Each SELECT statement creates a plot for a preceding REPORT statement. For example, three separate REPORT statements followed by two separate SELECT statements would produce six plots (see Control-statement-examples-for-PRSPLT00).

SELECT={ALL | TRANCODE=(id,...,*) | MSGREGION=(id,...,*) |

LTERM=(id,...,*) | RTCODE=(id,...,*) | DATABASE=(id,...,*)}

Parameter

Description

ALL

Selects all transactions that satisfy date, time, system, and region type requests specified by the XAXIS control statement

TRANCODE

Requests one or more transactions by name, where id is a 1- to 8-byte character string name

An asterisk requests the previous list of transaction names. TRANCODE cannot be used to select program record data.

MSREGION

Requests one or more message regions by name, where id is a 1- to 8-byte character string name

An asterisk requests the previous list of region names. Program and transaction records can be plotted (see CA, CU, EP, PE, PS, SA, UA, MP, and TC in REPORT-control-statement).

LTERM

Requests one or more LTERMs by name, where id is a 1- to 8-byte character string name

An asterisk requests the previous list of LTERM names. LTERM requests can be made against a detailed IRUF only. This parameter cannot be used to select program record data.

RTCODE

Requests one or more routing codes by name, where id is a 1- to 8-byte character string name

An asterisk requests the previous list of RTCODE names. Fast-Path-specific transaction data can be plotted (see BU, BW, CC, OW, and SF in REPORT-control-statement).

DATABASE

Requests one or more DL/I databases or DB2 application plans by name, where id is a 1- to 8-byte character string name

An asterisk requests the previous list of database names. Only data within the database segments of the transaction record can be plotted (see AQ, ER, DN, DR, PI, and S in REPORT-control-statement).

Database selection is not valid for REPORT=AW, because the wait-time calculations are done with transaction-level data.

 

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