Sharing terminal definitions

This section applies to all supported types of non-z/OS Communications Server terminals.

With the exception of SYSIDNT, the operands of DFHTCT TYPE=REMOTE form a subset of those that can be specified with DFHTCT TYPE=TERMINAL. Any of the remaining operands can be specified. They are ignored unless the SYSIDNT operand names the local system, in which case the macro becomes equivalent to the DFHTCT TYPE=TERMINAL form.

A single DFHTCT TYPE=REMOTE macro can therefore be used to define the same terminal in both the local and the remote systems. A typical use of this method of definition is shown in Figure 1.
Figure 1. Typical use of DFHTCT TYPE=REMOTE macro
  Local System CICL                  Remote System CICR
        AOR                                 TOR        

DFHSIT TYPE=                       DFHSIT TYPE= 
       SYSIDNT=CICL                       SYSIDNT=CICR
                                                      
DFHTCT TYPE=INITIAL,               DFHTCT TYPE=INITIAL,
       ACCMETH=NONVTAM,                   ACCMETH=NONVTAM,
       SYSIDNT=CICL,                      SYSIDNT=CICR,
       .                                  .            
       .                                  .            
                                                       
DFHTCT TYPE=REMOTE,                DFHTCT TYPE=REMOTE,
       SYSIDNT=CICR                       SYSIDNT=CICR
       TRMIDNT=aaaa,                      TRMIDNT=aaaa,
       TRMTYPE=3277,                      TRMTYPE=3277,
       TRMMODL=2,                         TRMMODL=2,  
       ALTSCRN=(43,80)                    ALTSCRN=(43,80)
       .                                   .          
       .                                   .          
DFHTCT TYPE=FINAL                  DFHTCT TYPE=FINAL  
Note: VTAM® is now z/OS® Communications Server.

In Figure 1, the same terminal definition is used in both the local and the remote systems.

In the local system, the fact that the terminal sysidnt differs from that of the local system (specified on the DFHTCT TYPE=INITIAL macro) causes a remote terminal entry to be built. In the remote system, the fact that the terminal sysidnt is that of the remote system itself causes the TYPE=REMOTE macro to be treated exactly as if it were a TYPE=TERMINAL macro.

Note: For this method to work, the CONNECTION from the local system to the remote system must be given the name of the sysidnt by which the remote system knows itself (CICR in the example).

The terminal identification is "aaaa" in both systems.



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