Shipping terminals for ATI requests
If you require a transaction that is started by ATI to acquire a remote terminal, you normally statically define the terminal to the AOR and any intermediate systems.
You do this because, for example, specifying a remote terminal for an intrapartition transient data queue (see Defining intrapartition transient data queues) does not cause a terminal definition to be shipped from the remote system. However, if a shipped terminal definition has already been received, following a previous transaction routing request, the terminal is eligible for ATI requests.
However, if the TOR and AOR are directly connected, CICS does allow you to cause terminal definitions to be shipped to the AOR to satisfy ATI requests. If you enable the user exit XALTENF in the AOR, CICS invokes this exit whenever it meets a “terminal-not-known” condition. The program you code has access to parameters, giving details of the origin and nature of the ATI request. You use these to decide the identity of the region that owns the terminal definition you want CICS to ship for you. A similar user exit, XICTENF, is available for start requests that result from EXEC CICS START.
Remember that XALTENF and XICTENF can be used to ship terminal definitions only if there is a direct link between the TOR and the AOR. See Shipping terminals for automatic transaction initiation for more information.
If you function ship START requests from a terminal-owning region to the application-owning region, you may need to consider using the FSSTAFF (function-shipped START affinity) system initialization parameter. See Shipping terminals for ATI from multiple TORs for more details.
A better way of handling terminal-related START requests is to use the enhanced routing methods described in Routing transactions invoked by START commands. If the START request is issued in the TOR, it is not function-shipped to the AOR: thus the “terminal-not-known” cannot occur; nor do you need to use FSSTAFF to prevent the transaction being started against the “wrong” terminal. Instead, the START executes directly in the TOR, and the transaction is routed as if it had been initiated from a terminal. If you are using shippable terminals, a terminal definition is shipped to the AOR if required.