‘Terminal not known’ condition exits XALTENF and XICTENF
The ‘terminal not known’ condition can occur when intercommunicating CICS® regions use both SHIPPABLE terminal definitions and automatic transaction initiation (ATI). The condition is especially likely to arise if autoinstall is used.
- SHIPPABLE attribute
- Terminals defined with the SHIPPABLE attribute in a terminal-owning region (TOR) do not need a definition in a connected application-owning region (AOR). If necessary to support transaction routing, CICS ships a copy of the definition from the TOR to the AOR. For further information, refer to Shipping terminal and connection definitions.
- Automatic transaction initiation (ATI)
- ATI occurs when an internally generated request leads to the initiation
of a transaction. For example, when:
- An application issues an EXEC CICS START command, or
- The transient data trigger level is reached.
The interval control program processes a START command, checks that the terminal is known in the local system, and (when any START time interval elapses) calls the terminal allocation program.
The terminal allocation program is called by the interval control program or by the transient data triggering mechanism, and checks that the terminal is known in the local system. If the requested terminal is remote, the terminal allocation program ships an ATI request to the remote system, which initiates transaction routing back to the local system.
For guidance information about ATI, refer to Traditional routing of transactions started by ATI.
- ‘Terminal not known’ condition
- The ‘terminal not known’ condition arises when an ATI request is made
for a terminal not known in the region. An ATI request can occur in the AOR
for a SHIPPABLE terminal before any transaction routing has taken place for
the terminal, and so before the definition of the terminal can have been shipped
from the TOR to the AOR.
If the ‘terminal not known’ condition occurs, both the interval control program and the terminal allocation program reject the transaction-initiation request as ‘TERMIDERR’.