Static routing of terminal-related START commands

Transactions that are statically routed specify ROUTABLE(YES) and DYNAMIC(NO) in the transaction definition in the terminal-owning region, so that the dynamic routing program is not called.

If the transaction is eligible for enhanced routing, the following steps take place:
  1. The START command runs in the TOR.
  2. The transaction is routed to the AOR named in the REMOTESYSTEM option of the transaction definition. If REMOTESYSTEM is not specified, the transaction runs locally, in the TOR.

If the transaction is not eligible for enhanced routing, the START request is handled in the usual way, described in Traditional routing of transactions started by ATI; that is, it is function-shipped to the AOR named in the REMOTESYSTEM option of the transaction definition. If REMOTESYSTEM is not specified, the START request runs locally in the TOR.

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 a TOR.
Figure 1. Static routing of a terminal-related START command issued in a TOR, 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 the AORs are MRO or APPC single- or parallel-sessions. A terminal-related transaction, TRAN1, is defined as DYNAMIC(NO) ROUTABLE(YES) REMOTESYSTEM(AOR3) in the TOR.A program on the TOR issues an EXEC CICS START TRANSID(TRAN1) TERMID(T1) request. CICS routes the request to AOR3.TOR is the requesting and routing region. AOR3 is the target region.

The TOR and the target region are connected by an IPIC, MRO or APPC (single or parallel session) link. The transaction definition in the TOR specifies DYNAMIC(NO) and ROUTABLE(YES). The REMOTESYSTEM option names the AOR to which the transaction is to be routed.



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