Restricting identifiers for selected report sets
Use the Trace Qualification window to filter the data to be collected by the collect task.
About this task
If you selected the Requesting Location, Plan
name and Authid field in the Trace Configuration window,
the Trace Qualification window (Figure 1)
is displayed. Only data from threads that match the trace qualification
criteria in this window will be collected. These trace qualification
criteria are also used if thread termination is indicated in the Trigger
by Time window (Figure 1).
┌-------------------------------------------------------------------------┐
| DGOMAP33 Trace Qualification |
| |
| Task description . . . . . . : Collect data for acct/stats/audit |
| |
| |
| Change values as desired: |
| |
| Requesting Location . . . . . . __________________ __________________ |
| __________________ __________________ |
| __________________ __________________ |
| __________________ __________________ |
| |
| Plan name . . . . . . . . . . . ________ ________ ________ ________ |
| ________ ________ ________ ________ |
| |
| Authid . . . . . . . . . . . . ________ ________ ________ ________ |
| ________ ________ ________ ________ |
| |
| Command ===> __________________________________________________________ |
| F1=Help F2=Split F3=Exit F9=Swap F12=Cancel F16=Look |
└-------------------------------------------------------------------------┘
Specify the name of the requesting location, plan name, and authorization ID, then press Enter. Do not specify multiple entries for more than one identifier, otherwise the number of Db2 traces started by the collect task could exceed the Db2 limit of 32 traces.
Trace qualification does not apply to all IFCIDs. Some system-related traces are collected regardless of the trace qualification criteria specified in the Trace Qualification window, for example, traces for IFCIDs 1, 2, 4, 104, 105, 106, and 202.