This section provides an overview of the RECTRACE command.
Usage
Use the RECTRACE command to generate Record
traces and file data sets.
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 RECTRACE command
Notes:
1 You can specify TRACE up to 5 times.
2 FILE can be specified only once.
Subcommands
The subcommands are described in detail,
together with their various options, in the following sections.
Sample JCL for requesting Record trace functions
The following is a sample of the JCL required to produce Record
traces. For details about the JCL and DD statements used, see The OMEGAMON for Db2 PE command stream. Figure 1. Sample JCL for requesting Record trace
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
//RTTRCDD1 DD SYSOUT=*
//RTFILDD1 DD DSN=MYID.FPELIB.RTFIL.DATA,DISP=OLD
//RTWORK DD DSN=MYID.FPELIB.RT.WORKDD,DISP=OLD
//* FOLLOWING IS THE COMMAND STREAM
//SYSIN DD *
RECTRACE
TRACE
FILE
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: The OMEGAMON for Db2
PE command stream
is only processed if EXEC is included as the last command. Otherwise, OMEGAMON for Db2
PE only checks the
syntax.