Report Command Reference - SQLACTIVITY command

SQLACTIVITY command

This section provides an overview of the SQLACTIVITY command.

Usage

Use the SQLACTIVITY command to reduce data, and to generate reports and traces.

Usage notes

This command can be used once in a job step, it can be used in the same job step with other report set commands.
For migration purposes you can use the SQLACTIVITY command to find information that was previously contained in the following report subjects for ACCOUNTING report types of the OMEGAMON® Historical Reporter:
- SCAN_ACTIVITY
- SORT_ACTIVITY
- SUMMARY
- DETAIL
You can filter records with the GLOBAL command first. This can minimize your report output and reduce processing time. See GLOBAL command for more information.

Syntax of the SQLACTIVITY command

                                   (1)
                .-TRACE subcommand-------.
>>-SQLACTIVITY--+------------------------+---------------------><
                |                   (2)  |
                '-REPORT subcommand------'

Notes:

You can specify TRACE up to 5 times.
You can specify REPORT up to 5 times.

Subcommands

The subcommands are described in detail, together with their various options, in the following sections.

Sample JCL for requesting SQL Activity functions

The following figure is a sample of the JCL required to produce SQL Activity reports and traces. A description of the DD statements follows the sample.

Figure 8. Sample JCL for requesting SQL Activity functions

 //       PEMAIN EXEC PGM=FPECMAIN
 //* FOLLOWING ARE SYSTEM DDNAMES
 //STEPLIB  DD  DSN=FPE.FPELIB.RKANMOD,DISP=SHR
 //DPMPARMS DD  DSN=MYID.FPELIB.DPMPARMS,DISP=SHR
 //INPUTDD  DD  DSN=MYID.FPELIB.DPMIN,DISP=SHR
 //DPMLOG   DD  SYSOUT=*
 //SYSOUT   DD  SYSOUT=*
 //JOBSUMDD DD  SYSOUT=*
 //SYSPRMDD DD  SYSOUT=*
 //DPMOUTDD DD  DSN=MYID.FPELIB.DPMOUT.DATA,DISP=OLD
 //SYSUDUMP DD  DUMMY
 //* FOLLOWING ARE REPORT SET DDNAMES
 //SQTRCDD1 DD  SYSOUT=*
 //SQRPTDD  DD  SYSOUT=*
 //SQLWORK  DD  DSN=MYID.FPELIB.SQL.WORKDD,DISP=OLD
 //* FOLLOWING IS THE COMMAND STREAM
 //SYSIN   DD  *

·
·
·

SQLACTIVITY
   TRACE
   REPORT

·
·
·

EXEC

The OMEGAMON XE for DB2® PE command language shown in this section is not appropriate in all circumstances. You must modify it to meet your requirements.

Most of the DD statements with a SYSOUT destination do not have to be specified because they are dynamically allocated by OMEGAMON XE for DB2 PE.

Note:

There is an advantage in omitting DPMOUTDD from your JCL. For more information, see DPMOUTDD statement.
The OMEGAMON XE for DB2 PE command stream is only processed if EXEC is included as the last command. Otherwise, no report is generated. OMEGAMON XE for DB2 PE checks the syntax of your command stream and writes it, together with any information, warning, or error messages generated.