Transaction routing enables a terminal in one CICS® system to run with a transaction in another CICS system. The typical way to initiate transaction routing is by entering a remote transaction ID at a local terminal. For other ways, see the CICS Family: Interproduct Communication manual.
Transactions can be routed in either direction over an LU 6.2 link between any CICS non-System/390® system and any CICS on System/390 system.
For transaction routing from a CICS on System/390 system, CICS on System/390 requires a remote definition of the non-System/390 transaction. The REMOTESYSTEM name must be the name of the connection to the non-System/390 system.
CICS on System/390 requires a local definition of the terminal from which the transaction is routed. The definition could be statically-defined or autoinstalled.
The non-System/390 CICS requires a remote definition of the terminal. This remote terminal definition could be statically-defined to the non-System/390 CICS or shipped from CICS on System/390.
For transaction routing from CICS Transaction Server for Windows, CICS on Open Systems, or CICS/400, the non-System/390 CICS requires a remote definition of the CICS on System/390 transaction (see the Intercommunication Guide or equivalent for the non-System/390 system).
The non-System/390 CICS requires a local definition of the terminal from which the transaction is routed.
CICS on System/390 requires a remote definition of the terminal. This remote terminal definition could be statically-defined to CICS on System/390 or shipped from the non-System/390 CICS.
The remote definition of a non-System/390 terminal has the following characteristics:
Dynamic transaction routing allows a user-written program (the "dynamic transaction routing program") to select the system to which a transaction routing request is to be directed. Dynamic transaction routing is supported by CICS on System/390, CICS on Open Systems, and CICS Transaction Server for Windows, but not by CICS/400.
The terminal-owning region (TOR) that receives the transaction request and the application-owning region (AOR) to which the request is routed do not have to be the same CICS product-type. For example, it is possible for a dynamic transaction routing program running on a CICS on System/390 TOR to route a transaction request to a CICS/400 AOR.
CICS on System/390 systems do no data conversion for transaction routing. Screen data always flows as 3270 data streams. COMMAREAs and TCTUAs (which are relevant to pseudoconversational transactions) are converted by the ASCII system.
There are some restrictions on transaction routing support, as follows: