Batch trace print
There are different types of input:
One or more trace log data sets
For example, a trace log data set of the Thread History trace.
Archived trace logs (without reloading to VSAM)
For example, thread history from two weeks ago.
- Data Collector archive files
- SMF history file containing Db2 Accounting records or I/O trace IFCIDs
- Live SMF data sets
- GTF trace data set
A batch utility job, DZTBTRAC, is provided in your BBSAMP data set to print these reports. There is also a sample JCL member DZTBPRNT you can use when you want to generate multiple reports or print accounting reports from SMF data. The control statements for several sample reports are provided in BBSAMP member DZJPnnnn, with comments to point out some of the most useful variations.
The trace data shown in the batch reports is in the same format and content as the online displays. This includes LTRAC, STRAC, DTRAC, DTRAC pop-ups, TSTAT, and the TSUMx series of displays. Many of these displays can also be combined into one report. For example, a report can consist of both LTRAC and DTRAC data. Selection options, such as plan, authorization ID, or date can be used to narrow the scope of a report. In addition, you can focus in on one area of interest, such as buffer pool activity by individual pool.
All of the report options described in Reference-of-offline-reports are also available by directly editing and submitting the batch trace print job, first specifying the input file and the reports to be printed.
This section contains the following topics: