Defining remote resources for transaction routing
CICS® transactions can be routed to remote regions either statically or dynamically.
A transaction that is to be routed may be started in a variety
of ways:
- From a user terminal.
- By a terminal-related ATI request; for example, a terminal-related EXEC CICS START command.
- By a non-terminal-related ATI request; for example, by a non-terminal-related EXEC CICS START command.
- If the transaction is associated with a CICS business transaction services (BTS) activity, by a BTS RUN ASYNCHRONOUS command. For more information about BTS, see Overview of BTS.
To route these requests, you must define a routing program. CICS provides two routing programs that can route different types of request: the dynamic routing program and the distributed routing program. For more information about these programs, see Two routing programs. To route requests between CICS regions, you must specify the appropriate program in the associated system initialization parameter:
- If you use the distributed routing program, specify the DSRTPGM system initialization parameter in each routing and target CICS region.
- If you use the dynamic routing program, specify the DTRPGM system initialization parameter in each routing region.
In addition to configuring the CICS region, you must define the
appropriate CICS resources:
- If the request to start the transaction is associated with a terminal, define the terminal. For more information, see Defining terminals for transaction routing.
- For every request, define a TRANSACTION resource with the appropriate attributes. For more information, see Defining transactions for transaction routing.