Report Command Reference

AUDIT command

This section provides an overview of the AUDIT command.

Usage

Use the AUDIT command to reduce data and generate Audit reports, traces, and file data sets. The subcommands are described in detail, together with their various options, in the following sections.

Usage notes

This command can be used once in a job step.
However, it can be used in the same job step with commands of the other report sets.
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

                              (1)
          .-REPORT subcommand------.
>>-AUDIT--+------------------------+---------------------------><
          |                   (2)  |
          +-REDUCE subcommand------+
          |                  (3)   |
          +-TRACE subcommand-------+
          |                 (4)    |
          '-FILE subcommand--------'

Notes:

You can specify REPORT up to 5 times.
You can specify REDUCE only once. If specified, you must also specify REPORT, TRACE, or FILE at least once.
You can specify TRACE up to 5 times.
You can specify FILE up to 7 times.

Subcommands

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

Sample JCL for requesting Audit functions

The OMEGAMON® XE for DB2® PE command language shown in this example 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. See DD statements for full descriptions of the DD statements.

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, OMEGAMON XE for DB2 PE only checks the syntax and writes the command stream together with any information, warning, or error messages generated to the job summary log.

This is a sample of the JCL required to produce Audit reports and traces. A description of the DD statements follows the sample.

Figure 4. Sample JCL for requesting Audit 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=*
 //DPMOUTDD DD  DSN=MYID.FPELIB.DPMOUT.DATA,DISP=OLD
 //SYSUDUMP DD  DUMMY
 //* FOLLOWING ARE REPORT SET DDNAMES
 //AURPTDD  DD  SYSOUT=*
 //AUTRCDDx DD  SYSOUT=*
 //AUFILDDx DD  DSN=MYID.FPELIB.AUDIT.FILE,DISP=OLD
 //AUDWORK DD   DSN=MYID.FPELIB.AUDIT.WORKDD,DISP=OLD
 //* FOLLOWING IS THE COMMAND STREAM
 //SYSIN   DD  *


·
·
·

AUDIT
   REDUCE
   REPORT
   TRACE
   FILE

·
·
·

EXEC