Entries in terminal list table—DFHTLT TYPE=ENTRY

Entries are coded in the TLT as follows:
Read syntax diagramSkip visual syntax diagram
>>-DFHTLT--TYPE=ENTRY------------------------------------------->

              .-,-------------------------------------.     
              V                                       |     
>--,TRMIDNT=(---+----------------------+--+---------+-+-)------><
                '-termid-1--+--------+-'  '-/opid-1-'       
                            '-*ldc-1-'                      

TYPE=ENTRY
Code this if one or more entries are to be generated in this table, up to a maximum of 1000 entries.
TRMIDNT=([termid-1[*ldc-1]] [/opid-1][, termid-2[*ldc-2][/opid-2],...])
Code this with a list of start-stop and BSC terminal, logical unit, and operator identifications. A logical unit identification can be qualified by an LDC mnemonic.
termid
Indicates a 1- to 4-character start-stop or BSC terminal or logical unit identification.
Note: A 3614 attached to a communications controller may be used in master or supervisory terminal operations but should not be used in message switching operations. (A 3614 is not valid for a message destination.)
ldc
Indicates a 2-character LDC mnemonic, which must be preceded by an asterisk (*) and is only used following the 'termid' parameter to which it is appended.
opid
Indicates a 1- to 3-character operator identification that must be preceded by a slash (/).

Any terminal or operator identification specified should also be specified in the TRMIDNT operand of the DFHTCT macro and in your external security manager, respectively. (If you employ RACF®, you use the OPIDENT operand of the ADDUSER command to record the identification for each operator.) Any LDC mnemonic specified should also be specified in the LDC operand of the DFHTCT TYPE=LDC and DFHTCT TYPE=TERMINAL macros.

Supervisory and master terminal functions use the terminal and logical unit identifications included in the TLT, but ignore all references to LDC mnemonics and operator identifications.