Rules for coding trace selection parameters

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=DFHTU710,PARM=('TERMID=LP1,TRANID=(ABRW,AORD,MYTR)',
//         'TIMERG=(123000-150000)')
The following example, with the transaction ID MYTR placed in a second record, would not work, because the list has been split within the keyword rather than between keywords:
TRANID=(ABRW,AORD,   [Select entries for tranids ABRW, AORD...
MYTR),                     & MYTR
Figure 1. Association of transaction-attach trace entries with task entries
The figure shows an auxiliary trace data set with nine entries. The second and seventh entries in the data set are transaction-attach trace entries, and the rest of the entries are task entries. Each task entry includes a point ID, a task ID, and some trace data. The point ID is the four-character hexadecimal value representing a point within the domain. The trace points for transactions that have been terminal-attached are AP 1730, AP 1731, AP 1790, AP 1791, AP 17B0, AP 17B1, AP 17C0 and AP 17C1. AP represents the domain, and the four-character value is the point ID. The task ID is the ID for the instance of the transaction to which the task belongs, and it can be in various formats — in our example, one of the task entries is for the task ID of 000119, three are for the task ID of 000120, two are for the task ID of 000123, and one is for the task ID of 000124. The two transaction-attach trace entries include, among other things, a point ID, the four-character ID of the transaction (TRANID), and a task ID (TASKID) for that instance of the transaction. The task IDs are 000123 and 000124. These two transaction-attach trace entries have a trace point of XM 1102, the trace point for task-attached transactions (XM represents the transaction manager domain, and 1102 is the point ID within the domain). As they are task-attached, instead of including a terminal ID (TERMID), they include another task ID field (also called TASKID) naming the task that attached them, TCP. The transaction-attach trace entry with the task ID 000123 can be matched up with the two task entries containing that task ID, so even though all the items are entered at different places in the data set, you can find them using the TRANID from the transaction-attach trace entry. If the transaction-attach trace entry had a TERMID, you could use that for the same purpose, but our examples do not have a TERMID. The same applies to the transaction-attach trace entry for task ID 000124. However, the transaction-attach trace entries for the other two task IDs in our example, 000119 and 000120, are not present in the data set, so you cannot find the task entries for these task IDs by searching on TERMID or TRANID — the task entries do not include this information.
Note: The trace point for transactions that have been task-attached is XM 1102. The trace points for transactions that have been terminal-attached are AP 1730, AP 1731, AP 1790, AP 1791, AP 17B0, AP 17B1, AP 17C0 and AP 17C1.


dfha68n.html | Timestamp icon Last updated: Monday, 5 June 2017