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

Read syntax diagramSkip visual syntax diagramUTILITY REPORT subcommand1REDUCE subcommand2TRACE subcommand3
Notes:
  • 1 You can specify REPORT up to 5 times.
  • 2 You can specify REDUCE only once. If specified, you must also specify REPORT at least once.
  • 3 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 1. 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
 //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 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 for Db2 PE. See the individual DD statement descriptions for more information.
Note:
  1. There is an advantage in omitting DPMOUTDD from your JCL. For more information, see the DPMOUTDD statement.
  2. The OMEGAMON 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 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.