Terminal-not-known condition

The terminal-not-known condition frequently occurs because a terminal-related START command is issued in the terminal-owning region and function-shipped to the application-owning region, where the terminal is not yet defined.

Important:

If you can use the enhanced routing method described in Routing transactions invoked by START commands, a START command issued in a TOR is not function-shipped to the AOR; thus the terminal-not-known condition does not occur.

To ensure correct functioning of cross-region ATI, you could define your terminals to all the systems on the network that need to use them. However, you cannot do this if you are using autoinstall. See Autoinstall. Autoinstalled terminals are unknown to the system until they log on, and you rely on CICS to ship terminal definitions to all the systems where they are needed. (See Shipping terminal and connection definitions.) This works when routing from a terminal to a remote system, but there are cases where a system cannot process an ATI request, because it has not been told the location of the associated terminal.

The example shown in Figure 1 should make this clear:
  1. The operator at terminal T1 selects the menu transaction M1 on CICA.
  2. The menu transaction M1 runs and the operator selects a function that is implemented by transaction X1 in CICB.
  3. Transaction M1 issues the following command, then exits:
    EXEC CICS START
         TRANSID(X1)
         TERMID(T1)
  4. Because X1 is defined as a remote transaction owned by CICB, CICA function-ships the START command to CICB.
  5. CICB now processes the START command and, in doing so, tries to discover which region owns T1, because this is the region that has to execute the ATI request resulting from the START command.
  6. CICB can determine where to send the ATI request only if a definition of T1, resulting from an earlier routed transaction, is present. Assuming that no such definition exists, the interval control program rejects the START request with TERMIDERR.
Figure 1. Failure of an ATI request in a system where the termid is unknown
Graphic is described in preceding text.


dfht1c0053.html | Timestamp icon Last updated: Sunday, 4 June 2017