DB2 trace

The DB2® instrumentation facility component (IFC) provides a trace facility that you can use to record DB2 data and events.

Begin program-specific programming interface information.

With the IFC, however, analysis and reporting of the trace records must take place outside of DB2. You can use Tivoli® OMEGAMON® XE for DB2 Performance Expert on z/OS® to format, print, and interpret DB2 trace output. You can view an online snapshot from trace records by using Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS or other online monitors.

Each trace class captures information on several subsystem events. These events are identified by many instrumentation facility component identifiers (IFCIDs). The IFCIDs are described by the comments in their mapping macros, contained in prefix.SDSNMACS, which is shipped to you with DB2.

End program-specific programming interface information.

Minimizing the volume of DB2 trace data
The volume of data that DB2 trace collects can be quite large. Consequently, the number of trace records that you request might impact system performance.
Types of DB2 traces
DB2 trace can record several types of data, including: statistics, accounting, audit, performance, monitor, and global traces.
Recording SMF trace data
Each location is responsible for processing the SMF records produced by DB2 trace.
Recording GTF trace data
The default destination for the performance trace classes is the generalized trace facility (GTF). The z/OS operator must start GTF before you can send data to it.
DB2 trace output
When you activate a DB2 trace, it produces trace records based on the parameters you specified for the START TRACE command.

Parent topic: Monitoring and analyzing DB2 performance data

Related concepts:

DB2 trace output

Programming for the instrumentation facility interface (IFI)

Related reference:

-START TRACE (DB2)

Related information

Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS

Tivoli OMEGAMON XE for Tivoli OMEGAMON XE for DB2 Performance Monitor for z/OS