Local and remote names for terminals

CICS® uses a unique identifier for every terminal that is involved in transaction routing. The identifier is formed from the applid (netname) of the CICS system that owns the terminal and the terminal identifier specified in the terminal definition on the terminal-owning region.

If, for example, the applid of the CICS system is PRODSYS and the terminal identifier is L77A, the fully-qualified terminal identifier is PRODSYS.L77A.

The following rules apply to all forms of hard-coded remote terminal definitions:
  • The definition must enable CICS to access the netname of the terminal-owning region. For example, if you are using z/OS® Communications Server terminals and there is no direct link to the TOR, you should use the REMOTESYSNET option to provide the netname of the TOR.

    If you are using non-z/OS Communications Server terminals and there is no direct link to the TOR, the SYSIDNT operand of the DFHTCT TYPE=REMOTE or TYPE=REGION macro must specify the name of an indirect link (on which the NETNAME option names the applid of the TOR).

  • The “real” terminal identifier must always be specified, either directly or by means of an alias.


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