Dynamic routing for commands issued in the AOR

Dynamic routing takes place if the transaction definition in the application-owning region (AOR) specifies ROUTABLE(YES) and the transaction definition in the terminal-owning region (TOR) specifies DYNAMIC(YES). Therefore, the dynamic routing program is invoked in the TOR.

Dynamic routing of transactions called by terminal-related START commands uses the hub routing model described in The hub model.

If the transaction is eligible for enhanced routing, the routing program can reroute the transaction to an alternative AOR; that is, to an AOR other than that in which the START was issued.

If the transaction is not eligible for enhanced routing, the dynamic routing program is called for notification only; it cannot reroute the transaction. The transaction is handled in the usual way; that is, it is routed back to the originating AOR for execution.

Figure 1 shows the requirements for dynamically routing a transaction that is initiated by a terminal-related START command issued in an AOR.
Figure 1. Dynamic routing of a terminal-related START command issued in an AOR
A TOR is connected to four AORs. AOR1 is the requesting region. TOR is the routing region. AOR3 is the target region. A terminal-related transaction, TRAN1, is defined as ROUTABLE(YES) in AOR1 and as DYNAMIC(YES) in the TOR. A program on AOR1 issues an EXEC CICS START TRANSID(TRAN1) TERMID(T1) request. CICS ships the request to the TOR for routing. In the TOR, the dynamic routing program runs and routes the request to AOR3.

The requesting region and the TOR are connected by an MRO, APPC, or IPIC parallel-session link. The TOR and the target region are connected by an MRO, APPC, or IPIC (single-session or parallel-session) link. The transaction definition in the requesting region specifies ROUTABLE(YES). The transaction definition in the TOR specifies DYNAMIC(YES).

Dynamic routing using IPIC is supported in CICS TS 4.1 or later.



dfht1c0061.html | Timestamp icon Last updated: Sunday, 4 June 2017