Previous transaction data characteristics
Previous transaction data identifies the local or parent task of a request to attach a task by an EXEC CICS RUN TRANSID or EXEC CICS START command (when a new point of origin is not created), and creates a trail that can be followed to the transaction that initiated the request, which enables data gathering and monitoring to continue in the region that initiated the request.
Previous transaction data is created if a request to attach a task is made by an EXEC CICS RUN TRANSID command, or some START commands, such as when the START command is not a new point of origin. The task that is attached as a result of this request has previous transaction data created.
Previous transaction data is not created for a task that is the point of origin. For information about association data, see Association data and for more information about the point of origin, see Origin data characteristics.
The value of previous transaction data for a task that is started by use of the START command depends on the TERMID option. Previous transaction data is not created for a started task that is at a new point of origin.
For a START command, the previous transaction data follows the same conventions as for previous hop data. For more information, see Previous hop data characteristics.
Previous transaction data programming considerations
- The task in the same local region that requested the current task to be attached.
- The current task depth from one task to another in the same CICS system with which this task is associated. A value of zero is the point of origin CICS system, or the first transaction that has been the result of a request from one CICS system to another to initiate a task.
Previous transaction data, when combined with previous hop data, identifies both the local and remote sender of a request to attach a task, and creates a trail that can be followed to the previous task or previous system, which enables data gathering to ocntinue in the region that sent the request.