Defining remote non-z/OS Communications Server terminals
Non-z/OS Communications Server terminals must be defined using resource definition macros: you cannot use RDO.
A remote non-z/OS Communications Server terminal requires a full terminal control table entry in the remote system (TOR), and a terminal control table entry in the local system (AOR) that contains sufficient information about the terminal to enable CICS® to perform the transaction routing. Data set control information and line information is not required for the definition of a remote terminal.
Non-z/OS Communications Server terminal definitions are not shippable.
Using resource definition macros, you can define remote non-z/OS
Communications Server terminals in either of two ways:
- By means of DFHTCT TYPE=REMOTE macros
- By means of normal DFHTCT TYPE=TERMINAL macros preceded by a DFHTCT TYPE=REGION macro
Both methods allow the same terminal definitions to be used to generate the required entries in both the local and the remote system.