Remote definitions for terminals for transaction routing

There are two possible methods of defining the terminals using macros. (There is another method, only possible using RDO, called 'shipping terminal definitions'. See Terminals for transaction routing.) The two macro methods are:
  • Method 1:
     
    DFHTCT TYPE=REGION, ...   (one for each region)
     
    DFHTCT TYPE=SDSCI, ...    (for non-VTAM terminals only;
                               ignored for remote definitions)
     
    DFHTCT TYPE=LINE, ...     (for non-VTAM terminals only)
     
    DFHTCT TYPE=TERMINAL, ... (for non-VTAM: one for each terminal)
     
  • Method 2:
     
    DFHTCT TYPE=REMOTE, ...   (one for each terminal)
     

Start of changeBoth methods allow the same terminal definitions to be used to generate the required entries in both the local and the remote system.End of change

Method 1:
You can use copybooks to include the same source code in the TCTs for local and remote systems. The information not needed (that is, the whole of the TYPE=SDSCI macro, and some of the TYPE=LINE and TYPE=TERMINAL macros) is discarded for remote entries.
CICS decides whether to create a remote or a local definition on the basis of the SYSIDNT operand on the TYPE=REGION macro. This is compared with the SYSIDNT operand in DFHTCT TYPE=INITIAL. If they are the same, the definition(s) are local. If they are different, the definition(s) are remote.
Note: Start of changeCICS® TS 3.1 does not support local TCAM terminals and therefore does not build local definitions of TCAM terminals.End of change
Method 2:
Employs a single DFHTCT TYPE=REMOTE macro.
CICS decides whether to create a remote or a local definition on the basis of the SYSIDNT operand on the TYPE=REMOTE macro. This is compared with the SYSIDNT operand in DFHTCT TYPE=INITIAL. If they are the same, the definition(s) are local. If they are different, the definition(s) are remote.
Note: Start of changeCICS TS for z/OS®, Version 3.1 does not support local TCAM terminals and therefore does not build local definitions of TCAM terminals.End of change
These terminals cannot use transaction routing and therefore cannot be defined as remote:
  • IBM® 7770 or 2260 terminals
  • MVS™ system consoles
  • Pooled TCAM terminals
  • Pooled 3600 or 3650 Pipeline Logical Units