transactionID

For COBOL transaction-oriented environments such as CICS® or IMS™, sysVar.transactionID contains the name of the transaction code for the next program segment. For batch environments, the setting of sysVar.transactionID is ignored.

In Java™ environments, if the program was invoked by a transfer to program statement, the variable contains the name of the transferring program.

Characteristics

Characteristics of sysVar.transactionID are as follows:
Primitive type
CHAR
Data length
8
Value saved across segmented converse?
Yes

Compatibility

Table 1. Compatibility considerations for sysVar.transactionID
Platform Issue
CICS sysVar.transactionID acts as follows:
  • Changes the transaction ID that is used to invoke the program after a converse statement in a segmented program.
  • Initially contains the value specified for the restartTransactionID build descriptor option or (in the absence of that value) contains the transaction ID used to invoke the program, except that if the program was invoked by a transfer to program statement, the variable initially contains the transaction ID of the transferring program.

    If the CICS-based program is running in a Web application, the variable contains the transaction ID for the catcher program DFHMIRS.

IMS BMP
  • If the program runs as a batch-oriented BMP, sysVar.transactionID is ignored.
  • If the program runs as a transaction-oriented BMP, sysVar.transactionID is reset to the transaction code from the IMS message header each time there is a successful get next that reads a serial file associated with the I/O PCB.
IMS/VS
  • For transaction programs, the initial value of sysVar.transactionID for the first program is the IMS transaction code used when the program is started.
  • For a batch program that uses get next to read a serial file associated with the I/O PCB, sysVar.transactionID is reset to the transaction code from the IMS message header each time a get next results in a successful get unique (GU) call.

Feedback