Default language.

Application trace services

This section describes the application trace services. Application trace comprises the data collection and data display services.

These services track the processing of specific threads through Db2 and display the time stamps, resource usage, and other important workload statistics for each thread (Db2 accounting record) traced. The services use selected Instrumentation Facility Component IDs (IFCID) obtained through the Db2 Instrumentation Facility Interface (IFI).

Related topic

Using the application trace facility

The following table shows the services used in the application trace.

Service

Title

Reference

Data Collection Area

ATRAC

DB2 APPLICATION TRACE

Trace Displays Area

LTRAC

DB2 TRACE ENTRIES

TSTAT

TRACE STATISTICS

TSUMA

TRACE SUMMARY BY AUTHID

TSUMC

TRACE SUMMARY BY CONNECT

TSUML

TRACE SUMMARY BY LOCATION

TSUMP

TRACE SUMMARY BY PLAN

TSUMR

TRACE SUMMARY BY CORRID

TSUMT

TRACE SUMMARY BYTIME

STRAC

SUMMARY TRACE ENTRY

DTRAC

DETAIL TRACE ENTRY

UTRAC

USER DETAIL TRACE

The ATRAC service (DB2 APPLICATION TRACE) is a timer-driven service that can be activated multiple times (with different selection criteria and trace types) to trace selectable workloads. The display services show the data collected by an ATRAC request.

Important

Data collection for a trace must be activated by the ATRAC service before the data can be displayed by the application trace display services. The appropriate Db2 traces are activated through the Instrumentation Facility Interface (IFI).

A trace entry is made in an internal buffer for each Db2 accounting record selected with the ATRAC service request as described in Collecting-trace-data. These entries are sometimes referred to as transactions, because this terminology is used generally by online systems such as IMS and CICS.

This section contains the following topics:




 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*