SQLACTIVITY command with REPORT subcommand
This section describes the SQLACTIVITY command with the REPORT subcommand.
Usage
Use the REPORT subcommand to generate reports from records.
Usage notes
- Up to five REPORT subcommands can be specified within each SQLACTIVITY command.
Syntax of the REPORT subcommand
Subcommand options
The syntax diagram shows the options that are available with this subcommand. See Subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.
- FROM/TO
- Limits
the range of records included in the reporting process by date and
time.
For details, see FROM/TO subcommand options.
- SUMMARIZEBY
- Selects the SQL events to be summarized. You can specify one entry
of SUMMARIZEBY for each REPORT subcommand. The following events can
be specified:
- PROGRAM
- This is the default.
- CURSOR
- Cursor
- STMTID
- Statement ID
- STMTNO
- Statement number
- STMTTYPE
- Statement type
- ALL
- All of the above
For more information about summarization, see the Reporting User's Guide.
- SORTBY
- Sorts the SQL events within each summary level within each thread.
You can specify one entry of SORTBY for each REPORT subcommand. One
of the following events can be specified:
- DEFAULT
- The default sort sequence depends on the summary level specified.
- ELAPSEDTIME
- Average elapsed time
- EXITS
- Number of exits
- EXITTIME
- Elapsed time for each exit
- IOREQS
- I/O requests
- IOTIME
- Elapsed time for each I/O request
- PAGESCAN
- Pages scanned
- ROWSPROC
- Rows processed
- SCANS
- Number of scans
- SORTRECS
- Records sorted
- SORTWORK
- Workfiles sorted
- SUSP
- Lock suspensions
- SUSPTIME
- Elapsed time for each lock suspension
- TCBTIME
- Average TCB time
For more information about sorting and default, see the Reporting User's Guide.
- WORKLOAD
- Displays workload detail for each event. The following detail
can be reported:
- NONE
- No workload activity. This is the default.
- ACCT
- Accounting
- ALL
- All workload activity
Including MINIBIND if IFCID 22 is included in the input.
Including UDF activity if IFCID 324 is included in the input.
Note that the more workload detail you request, the more time OMEGAMON® for DB2® PE requires for processing your request. It is recommended that you do not specify WORKLOAD(ALL) with a large amount of input data unless absolutely necessary.
- DCAP
- Data capture activity
- EXIT
- Exit activity
- HILITE
- Workload highlights
- IO
- I/O activity
- LOCK
- Lock suspension and page and row locking activity
- SCAN
- Scan activity, RID list activity, and query parallelism activity
- SORT
- Sort activity
Note: When IFCID 3 is included in the input, Accounting Trace activity is automatically included as part of the workload detail.For more information about workload detail, see the Reporting User's Guide and the Report Reference.
- DDNAME
- Specifies the data set where the report is written.
- ORDER
- Specifies the OMEGAMON for DB2 PE identifiers
and their sequence for sorting the report and, in summary reports,
which identifiers are used for aggregation.
For details, see ORDER subcommand option and OMEGAMON for Db2 PE identifiers.
- INCLUDE/EXCLUDE
- Includes or excludes data associated with specific OMEGAMON for DB2 PE identifiers.
For details, see INCLUDE and EXCLUDE subcommand options, which lists other identifiers allowed with this command and subcommand combination, and OMEGAMON for Db2 PE identifiers.
Example using REPORT with FROM, TO, and EXCLUDE options
- Records are used with the time and date range of 10:00 a.m. on 18 March 2002 to noon on 19 March 2002
- Data is excluded that is associated with the following locations:
- LOCN10
- LOCN12
- LOCN15
- LOCN20
⋮
REPORT
FROM (03/18/02,10:00:00.00)
TO (03/19/02,12:00:00.00)
EXCLUDE (LOCATION(LOCN10 LOCN12 LOCN15 LOCN20))
⋮