Report Command Reference - ORDER subcommand option

ORDER subcommand option

The ORDER subcommand option defines which OMEGAMON® XE for DB2® PE identifiers are used to aggregate records.

Usage

The ORDER subcommand option specifies which OMEGAMON XE for DB2 PE identifiers are used to aggregate records and, unless the TOP(ONLY) subcommand option is specified for Accounting, identifies the presentation sequence of the report entries.

Usage notes

You can specify one entry of ORDER for each REPORT subcommand.
You can order by one, two, or three identifiers separated by a dash, and you can specify up to five sets of the identifiers separated by at least one blank, a comma, or a new line.
For group-scope Locking reports, the default order is DATABASE-PAGESET. For all other reports, the default for ORDER is PRIMAUTH-PLANNAME.
MEMBER is automatically added as the second, third, or fourth identifier in group-scope reports.
In a distributed environment you should order your reports by REQLOC or CONNTYPE. If REQLOC or CONNTYPE are not used in the ORDER subcommand option of REPORT, the accounting portion of all threads, including DBATs, where the combination of OMEGAMON XE for DB2 PE identifiers is the same are reported as one entry.

Syntax

ORDER Block:
 
             .-(5)---------------------------------------.
             | .-PRIMAUTH-PLANNAME---------------------. |
             | | .- - --;--;--;(3)----------------------. | |
             V | V                                   | | |
|--ORDER--(----+---OMEGAMON XE for DB2 PE identifier-+-+-+--)---|

Rules

The table below shows the OMEGAMON XE for DB2 PE identifiers and criteria that can be used with the ORDER subcommand option.

Table 7. OMEGAMON XE for DB2 PE identifiers used with ORDER subcommand option
OMEGAMON XE for DB2 PE Identifier	Accounting	Audit	I/O Activity	Locking	SQL Activity	Statistics	Utility Activity
BPID (Buffer pool ID)			•
CLASS (DB2 trace class)	•	•	•	•	•		•
CONNECT (Connection ID)	•	•	•	•	•		•
CONNTYPE (Connection type)	•	•	•	•	•		•
CORRNAME (Correlation name)	•	•	•	•	•		•
CORRNMBR (Correlation number)	•	•	•	•	•		•
DATABASE (Database name)			•	•
ENDUSER (End user ID)	•	•		•	•
INSTANCE (Instance number)							•
INTERVAL (Interval)	•		•			•
MAINPACK (Main package)	•
OBJECT (Object type)		•
ORIGAUTH (Original authorization ID)	•	•	•	•	•		•
PACKAGE (Package information) or PROGRAM (Program information)	•
PAGESET (Page set name)			•	•
PLANNAME (Plan name)	•	•	•	•	•		•
PARTNBR (Partition number)			•
PRIMAUTH (Primary authorization ID) or AUTHID (Authorization ID)	•		•	•	•		•
REQLOC (Requester location)	•	•	•	•	•		•
TRANSACT (End user transaction name)	•	•		•	•
WSNAME (End user workstation name)	•	•		•	•
Note: For Utility Activity, the ORDER option can be used for both reports and traces. Instance number is applicable to Utility trace only.

Example of the ORDER subcommand option

The following example specifies that two reports are produced:

Both reports use the SHORT layout by default.
The first report is ordered by primary authorization ID within plan name within connection ID.
The second report is ordered by plan name within primary authorization ID.
Both reports are written to the data set with the default ddname ACRPTDD.


·
·
·

ACCOUNTING
   REPORT
      ORDER   (CONNECTION-PLANNAME-PRIMAUTH,PRIMAUTH-PLANNAME)

·
·
·