‘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
Terminalsdefined 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 theAOR. For further information, refer to the

CICS Resource

Definition Guide
.
Automatic transaction initiation (ATI)
ATI occurs when an internally generated request leads to the initiation of a
transaction. For example, when:
vAn application issues an EXEC CICS STARTcommand, or
vThe transient data trigger level is reached.
Two CICS modules handleATI requests:
The interval control program processes a STARTcommand, checks that the
terminal is known in the local system, and (when any STARTtime 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 ATIrequest to the remote system, which initiates transaction
routing back to the local system.
For guidance information about ATI,refer to the
CICS Intercommunication
Guide
.
‘Terminal not known’condition
The ‘terminal not known’ condition arises when anATI request is made for a
terminal not known in the region. AnATI 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 theAOR.
If the ‘terminal not known’ condition occurs, both the interval control program
and the terminal allocation program reject the transaction-initiation request as
‘TERMIDERR’.
The exits
Todeal with the ‘terminal not known’ condition, CICS provides global user exits in
the interval control and terminal allocation programs:
XICTENF
In the interval control program
XALTENF
In the terminal allocation program.
terminal not known condition exits
208 CICS TS for OS/390: CICS Customization Guide