Shipping terminals for ATI from multiple TORs
Consider the following network setup.
- You have an application-owning region that is connected to two or more terminal-owning regions (TORs) that use the same, or a similar, set of terminal identifiers.
- One or more of the TORs issues EXEC CICS START requests for transactions in the AOR.
- The START requests are associated with terminals.
- You are using shippable terminals, rather than statically defining remote terminals in the AOR.
Now consider the following scenario:
Terminal-owning region TORB issues an EXEC CICS START request for transaction TRANB, which is owned by region AOR1. It is to be run against terminal T1. Meanwhile, terminal T1 on region TORA has been transaction routing to AOR1; a definition of T1 has been shipped to AOR1 from TORA. When the START request arrives at AOR1, it is shipped to TORA, rather than TORB, for transaction routing from terminal T1.

- This is the preferred method.
Use the enhanced routing method described in Routing transactions invoked by START commands. A terminal-related START command issued in the terminal-owning region is not function-shipped to the AOR; thus it cannot be shipped back to the wrong TOR. Instead, the START executes directly in the TOR, and the transaction is routed as if it had been initiated from a terminal.
A definition of the terminal is shipped to the AOR, and the autoinstall user program is called. Your autoinstall user program can then allocate an alias termid in the AOR, to avoid a conflict with the previously installed remote definition. Terminal aliases are described in Terminal aliases. For information about writing an autoinstall program to control the installation of shipped definitions, see Writing a program to control autoinstall of shipped terminals.
- Use this method if you cannot use the enhanced routing method.
Code YES on the FSSTAFF system initialization parameter in the AOR. This ensures that, when a START request is received from a terminal-owning region, and a shipped definition for the terminal named on the request is already installed in the AOR, the request is always shipped back to a TOR, for routing, across the link it was received on, irrespective of the TOR referenced in the remote terminal definition. (The only exception to this is if the START request supplies a TOR_NETNAME and a remote terminal with the correct TOR_NETNAME is located; in which case, the request is shipped to the appropriate TOR.)
If the TOR to which the START request is returned is not the one referenced in the installed remote terminal definition, a definition of the terminal is shipped to the AOR, and the autoinstall user program is called. Your autoinstall user program can then allocate an alias termid in the AOR, to avoid a conflict with the previously installed remote definition.
For full details of the FSSTAFF system initialization parameter, see FSSTAFF system initialization parameter.