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.
