LOCKING command with TRACE subcommand

This section describes the LOCKING command with the TRACE subcommand.

Use the TRACE subcommand to produce traces with an entry for every Db2 locking event.

Usage notes

  • Up to five traces can be requested in a job step.

Syntax of the TRACE subcommand

Read syntax diagramSkip visual syntax diagram TRACEFROM/TO blockSCOPE(MEMBERGROUP)LEVEL(LOCKOUTSUSPENSIONDETAILDEADLOCKTIMEOUT)DDNAME(LOTRCDD*ddname)INCLUDE/EXCLUDE block

Subcommand options

The syntax diagram shows the options that are available with this subcommand. See Subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.

LEVEL
Specifies the type of trace and the amount of detail. One LEVEL option can be specified for each TRACE subcommand:
DETAIL
Generates a lock detail trace.
SUSPENSION
Generates a lock suspension trace.
LOCKOUT
Generates a lockout trace. This is the default.
DEADLOCK
Generates a deadlock trace.
TIMEOUT
Generates a timeout trace.
INCLUDE/EXCLUDE
Includes or excludes data associated with specific OMEGAMON for Db2 PE identifiers.

For details, see INCLUDE and EXCLUDE subcommand options, which lists other identifiers allowed with this command and subcommand combination, and OMEGAMON for Db2 PE identifiers.

Note that the identifier TYPE can only be used with LEVEL(DETAIL).

Example using TRACE with FROM and TO options

This example specifies that:
  • Three lockout (default) traces are produced for the time intervals specified.
  • Each trace covers a unique 10-minute period of time on the same day.
  • Each trace is written to the data set defined by the default ddname for the trace.
 
TRACE
   FROM (03/18/00,10:00:00.00)
   TO   (03/18/00,10:10:00.00)
TRACE
   FROM (03/18/00,11:00:00.00)
   TO   (03/18/00,11:10:00.00)
TRACE
   FROM (03/18/00,12:00:00.00)
   TO   (03/18/00,12:10:00.00)