Identifying trace entries from their transaction-attach entries
The AP domain writes a trace entry each time a transaction is attached for execution. It is this transaction-attach trace entry that contains the terminal and transaction identifiers. It also contains the task identifier that is unique to a particular instance of a transaction.
About this task
The association of transaction-attach trace entries with task entries is illustrated in the diagram shown in Figure 1.
If you select trace entries by specifying the TRANID or TERMID parameters, the DFHTU710 program searches for any transaction-attach trace entries that contain the specified TERMID or TRANID. It then formats any associated trace entries, identified by the TASKID found in the transaction-attach trace entry data.
For example, if the entries in your auxiliary trace data set are as illustrated in Figure 1, you can obtain formatted trace output for task IDs 00123 and 00124 by specifying the TRANID parameters. This is possible because the associated transaction-attach trace entries are present (see record numbers 2 and 7 in the diagram). Note that as the transactions in this example were task-attached, not terminal-attached, they do not have a TERMID. If they did have a TERMID, you could specify this to select the entries. However, you cannot obtain formatted trace output for task ID 00120 by specifying a TERMID or TRANID, because the auxiliary trace data does not contain the transaction-attach trace entry for that task.