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.
- The START command runs in the TOR.
- 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.

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.