You code the trace selection parameters to define the number of lines to be printed on a page and to define which trace records you want to select for printing in the DFHAXPRM DD statement, or in the PARM parameter. For example:
//PRINT EXEC PGM=DFHTU640,PARM='selection_parameter,selection_parameter,...'
If successive auxiliary trace entries are written at intervals equal or greater than this limit, they are highlighted in the same manner.
If successive auxiliary trace entries are written at intervals less than this limit, they are not highlighted. They are, however, written, formatted and printed.
If you specify no INTERVAL value, a default of 0.128 seconds applies.
You can specify interval values in the range zero seconds (where all trace entries would be highlighted) through 99.9999999999 seconds.
You can specify a range of task identifiers of the five decimal digit form by using a hyphen (for example, TASKID=nnnnn-nnnnn).
If you use the TERMID parameter to specify the trace entries you want formatted, the DFHTU640 program selects all the trace entries that are associated with any transaction-attach trace entries it finds containing the terminal identifier(s) you specify. For more information about how trace entries for tasks are associated with transaction-attach trace entries, see Identifying trace entries from their transaction-attach entries.
If you use the TRANID parameter to specify the trace entries you want formatted, the DFHTU640 program selects all the trace entries that are associated with any transaction-attach trace entries it finds that contain the transaction identifier(s) you specify. For more information about how trace entries for tasks are associated with transaction-attach trace entries, see Identifying trace entries from their transaction-attach entries.
The DFHTU640 program converts the store-clock (STCK) values in the trace entries to whole seconds prior to comparing against the time range you specify. Fractions of a second are ignored; that is, all times are rounded down to the nearest whole second, which means in effect that the minimum time span can be up to two seconds. For example, if you specify TIMERG=153000-153001, the DFHTU640 program includes all trace entries with times of 153000.00000000 to 153001.99999999 inclusive.
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. This is illustrated in the diagram shown in Figure 25.
If you select trace entries by specifying the TRANID or TERMID parameters, the DFHTU640 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 25, 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.
If you enter the control statements in the DFHAXPRM data set, enter them in columns 1 to 71 of the 80-character records. Leading blanks are ignored, and no imbedded blanks are allowed. The first blank in a line terminates the statements on that line; you can include comments after the first blank. The TERMID and TRANID entries are padded with blanks to four characters if necessary.
You can specify each control statement one or more times; for example,
TASKID(xxxx,zzzz,yyyy,aaaa,bbbb,cccc,dddd,eeee,ffff,gggg,hhhh,iiii,jjjj),
TASKID(kkkk,rrrr-uuuu,wwww)
You must use commas to separate keywords and entries in a list. Continuation to another record is allowed after any comma that separates keywords, provided the comma is in column 71 or is followed by a blank. Continuation records can start in any column.
For example, the following statements can be coded in DFHAXPRM:
TERMID=LP1, [Select entries for terminal LP1
TRANID=(ABRW,AORD,MYTR), [Select entries for tranids ABRW, AORD, & MYTR
TIMERG=(123000-150000)) [Select entries timed between 1230 and 1500
The same example could be coded in the PARM parameter as follows:
// EXEC PGM=DFHTU640,PARM=('TERMID=LP1,TRANID=(ABRW,AORD,MYTR)',
// 'TIMERG=(123000-150000)')
TRANID=(ABRW,AORD, [Select entries for tranids ABRW, AORD...
MYTR), & MYTR