UTILITY command with TRACE subcommand

This section describes the UTILITY command with the TRACE subcommand.

Usage

Use the TRACE subcommand to produce traces with an entry for each Db2 utility or bind event.

Usage notes

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

Syntax of the TRACE subcommand

Read syntax diagramSkip visual syntax diagramTRACEFROM/TO blockWORKLOAD(,NONEALLBINDEXITIOLOCKPHASE)TYPE(BIND UTILITYBINDUTILITY)ORDER blockDDNAME(UTTRCDD*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.

FROM/TO
Limits the range of records included in the trace by date and time.

For details, see FROM/TO subcommand options.

WORKLOAD
Displays the workload detail for each event. The following detail can be specified:
NONE
No workload activity. This is the default.
BIND
Bind activity
EXIT
Exit activity
IO
I/O activity
LOCK
Lock suspension and page and row locking activity
PHASE
Utility phases
ALL
All workload activity
TYPE
There are two activity types. You can select one or both of these activity types with each TRACE subcommand. If the TYPE subcommand option is omitted, both activity types are reported.
BIND
Gives the elapsed time for each occurrence of a bind event for each trace entry. This includes information on the number of bound and nonbound events and the distribution of the bind into various bind subevents.
UTILITY
Gives the elapsed time for each occurrence of a utility event for each trace entry, LISTDEF information, and information on the performance and resource and data set usage of the various utility events.
ORDER
Specifies the OMEGAMON for Db2 PE identifiers reported in the trace.

For details, see ORDER subcommand option and OMEGAMON for Db2 PE identifiers.

Note: Traces are printed in the order that the threads end in and are not sorted by these identifiers.
DDNAME
Specifies the data set where the trace is written.
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.

Example using TRACE with FROM and TO options

This example specifies:
  • A trace with no workload.
  • Including records from 10:00 to 10:15 on the input data set regardless of the date, because it was not specified.
  • Sent to UTTRCDD1 by default.
 
TRACE
   FROM  (,10:00)
   TO    (,10:15)