Thread history
The Data Collector provides an optimized collection of thread accounting records (DB2 IFCIDs 3 and 239), both by staging data upon receipt from DB2 in a data space, and by compressing the logged data.
This feature allows online access to a longer time period of thread history than in the THRDHIST trace log data sets, and also supports flexible batch reporting.
To streamline data access, you can specify thread-level or package-level filters prior to requesting package reports. You can access thread-level data from the Data Collector by accessing the HTLOGs view via the hyperlink on the CT view. Once in the HTLOGS view, you can then navigate to Thread History, then to the TRLTRAC and TRSTRAC views.
From the HTLOGS Thread History view, you can access Data Collector thread data from an entry with the Trace ID column containing an ID of MVDB2DC. BMC IFCIDs 350-352, which must be activated for tracing, provide this entry in HTLOGS and the thread interval history information in MainView for DB2 views. BMC IFCIDs 350-352 are activated when the Data Collector collects data for the MVDBACC data class for each DB2. We recommend that the MVDBACC data class is placed in its own Output Group.
For a list of the thread history views and a description of each, including HTLOGS, see Thread-interval-history and Thread-history-analysis.
For information about hyperlinking from HTLOGS, see Accessing-thread-history-data.
For examples of accessing thread history views from the HTLOGS view and filtering trace data, see the section on analyzing workload interval summaries in Analyzing-recent-workload-history.
Related topic