Dynamic routing of terminal-related START commands

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

Dynamic routing of transactions started by terminal-related START commands use the hub routing model.

If the transaction is eligible for enhanced routing, the following steps take place:
  1. The START command runs in the TOR.
  2. The routing program can route the transaction.

If the transaction is not eligible for enhanced routing, the dynamic routing program is started for notification only, because it cannot route the transaction. The START request is handled in the usual way; that is, it is function-shipped to the AOR named in the REMOTESYSTEM option of the transaction definition in the TOR. If REMOTESYSTEM is not specified, the START request runs locally in the TOR.

Figure 1 shows the requirements for dynamically routing a transaction that is initiated by a terminal-related START command issued in a TOR.
Figure 1. Dynamic routing of a terminal-related START command issued in a TOR
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(YES) ROUTABLE(YES) in the TOR.A program on the TOR issues an EXEC CICS START TRANSID(TRAN1) TERMID(T1) request. The dynamic routing program runs on the TOR and 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 both DYNAMIC(YES) and ROUTABLE(YES).



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