Static routing for commands issued in the AOR

Static 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(NO). Therefore, the dynamic routing program is not called.

If the transaction is eligible for enhanced routing, it is routed to the AOR named in the REMOTESYSTEM option of the transaction definition in the TOR. If REMOTESYSTEM is not specified, the transaction runs locally, in the TOR.

If the transaction is not eligible for enhanced routing, it is handled in the usual way, as described in Traditional routing of transactions started by ATI; that is, CICS tries to route it back to the originating AOR for execution. If the REMOTESYSTEM option of the transaction definition in the TOR names a region other than the originating AOR, the request fails.

Figure 1 shows the requirements for using the enhanced method to statically route a transaction that is initiated by a terminal-related START command issued in an AOR.
Figure 1. Static routing of a terminal-related START command issued in an AOR, using the enhanced method
The picture shows the scenario described in the preceding text. A TOR is connected to four AORs, AOR1 through AOR4. The links between the TOR and AOR1 are MRO or APPC parallel-session. The links between the TOR and AOR2 through AOR4 are MRO or APPC single- or parallel-sessions. A terminal-related transaction, TRAN1, is defined as ROUTABLE(YES) in AOR1 and as DYNAMIC(NO) REMOTESYSTEM(AOR3) in the TOR. A program on AOR1 issues an EXEC CICS START TRANSID(TRAN1) TERMID(T1) request. CICS ships the request to the terminal-owning region, TOR, for routing. TOR routes the request to AOR3.AOR1 is the requesting region. TOR is the routing region. AOR3 is the target region.
The requesting region and the TOR are connected by an IPIC, MRO or APPC parallel-session link. The TOR and the target region are connected by an IPIC, MRO or APPC (single- or parallel-session) link. The transaction definition in the requesting region specifies ROUTABLE(YES). The transaction definition in the TOR specifies DYNAMIC(NO). The REMOTESYSTEM option names the AOR to which the transaction is to be routed.


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