Report Command Reference - UTILITY command

UTILITY command

This section provides an overview of the UTILITY command.

Usage

Use the UTILITY command to generate Utility Activity reports and traces.

Usage notes

The 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 of the UTILITY command

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

Notes:

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

Subcommands

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

Sample JCL for requesting Utility Activity functions

The following figure is a sample of the JCL required to produce Utility Activity reports and traces. A description of the DD statements can be found in DD statements.

Figure 11. Sample JCL for requesting Utility 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
 //DISTDD   DD  DSN=MYID.FPELIB.DIST.DATA,DISP=OLD
 //SYSUDUMP DD  DUMMY
 //* FOLLOWING ARE REPORT SET DDNAMES
 //UTRPTDD  DD  SYSOUT=*
 //UTTRCDD1 DD  SYSOUT=*
 //UTWORK   DD  DSN=MYID.FPELIB.UT.WORKDD,DISP=OLD
 //* FOLLOWING IS THE COMMAND STREAM
 //SYSIN   DD  *

·
·
·

UTILITY
   REDUCE
   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. See the individual DD statement descriptions for more information.

Note:

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

Example using UTILITY together with DISTRIBUTE command

This example requests the following:

Generate frequency distribution information for field ID TBBTOTAL calculated over 15-minute intervals (using the default boundary) and include the primary authorization ID USER027 (the interval and the primary authorization ID to be included are specified in the REDUCE subcommand).
Create a trace, that presents the bind and DB2 Utility Activity (by default) in the period between 13:00 and 13:15 on the specified date.
Note:

The trace is written to the data set defined by the default ddname UTTRCDD1.
Create a Utility Activity report that includes bind and DB2 Utility Activity (by default).
Note:

The Utility Activity report is written to the data set defined by the default ddname UTRPTDD.


·
·
·

DISTRIBUTE       (FIELDID(TBBTOTAL))
UTILITY
   REDUCE
      INCLUDE  (PRIMAUTH(USER027))
      INTERVAL (15)
   TRACE
      FROM     (03/18/02,13:00:00.00)
      TO       (03/18/02,13:15:00.00)
   REPORT

·
·
·