Use the optional INTERPTCP mapping statement to allow you to map a customized interpret table to a Client Identifier. This table is used to interpret incoming USS commands before the USS command processor is invoked. If the input string does not match any interpret table entry, the USS command processor parses the input string.
Syntax
>>-INTERPTCP--table_name--+-----------------------------+------>< +-Client_Identifier-----------+ '-clid_type,Client_Identifier-'
Parameters
- table_name
- The name of the interpret table load module.
- clid_type
- Specifies the type of Client Identifier. It is required if USERID or DESTIP are specified. See Rules for client identifier specification for details.
- Client_Identifier
- One of several Client Identifiers. See Client identifier types and definitions for details. If no Client Identifier is specified, then it is considered the NULL Client Identifier.
Usage notes
- An assembled interpret table load module from VTAM® can be used or one can be created. See z/OS Communications Server: IP Configuration Guide for coding details. Also see Telnet INTERPRET table setup.
- Always map a unique Client Identifier on each INTERPTCP statement. Otherwise, the last INTERPRET table mapping for the Client Identifier is used.
- The most common setup error is to fail to include the table load module in a load library accessible by TCP/IP.
- The INTERPRET table is used to check USS commands only. Therefore, INTERPRET table function is provided only for connections that are using a USS table.