LOCKING command

This section provides an overview of the LOCKING command.

Usage

Use the LOCKING command to generate Locking reports, traces, and file data sets on locking-related DB2® data.

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

Read syntax diagramSkip visual syntax diagramLOCKING REPORT subcommand1REDUCE subcommand2TRACE subcommand3FILE subcommand4
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.
  • 4 You can specify FILE only once.

Subcommands

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

Sample JCL for requesting Locking functions

The following is a sample of the JCL required to produce Locking reports and traces. A description of the DD statements follows the sample.
Figure 1. Sample JCL for requesting Locking 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 DDNAMES
 //LOWORK   DD  DSN=MYID.FPELIB.LO.WORKDD,DISP=OLD
 //LORPTDD  DD  SYSOUT=*
 //LOTRCDD1 DD  SYSOUT=*
 //LOTRCDD2 DD  SYSOUT=*
 //LOTRCDD3 DD  SYSOUT=*
 //LOTRCDD4 DD  SYSOUT=*
 //LOTRCDD5 DD  SYSOUT=*
 //LOFILDD1 DD  DSN=MYID.FPELIB.LOFIL.DATA,DISP=OLD
 //* FOLLOWING IS THE COMMAND STREAM
 //SYSIN   DD  *

 
LOCKING
   TRACE
   REPORT
   FILE
 
EXEC
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 DD statements for descriptions and more information.
Note:
  1. There is an advantage in omitting DPMOUTDD from your JCL. For more information, see DPMOUTDD statement.
  2. If you do not include the EXEC statement in your JCL, no report is produced. The syntax of your JCL is checked and written to the DPMLOG data set together with any information, warning, or error messages raised.