INTERPTCP

In some cases, the application name must be generated based on the name provided by the user or the name might be dependent on the LU name representing the client. The INTERPRET table can provide this function. Telnet uses the input from the USSMSG10 screen as input to the INTERPRET table translation list or uses the USSMSG10 input and the LU name as input to one of the INTERPRET table user-written exits. Because USS logon data is required input to the INTERPRET process, any client with an INTERPRET table mapping must also have a USS table mapping. For example, use the following statement to map an INTERPRET table, INTTAB1, to any TN3270 or TN3270E client identified by the linkname LINK1. When a TN3270 or TN3270E client connects to LINK1, Telnet will immediately send a custom logon screen (USSMSG10) from the USS table. The user responds with a USS logon command. LINK1 client input is then processed through the INTTAB1 INTERPRET table to derive an application name. Telnet uses the derived name to initiate a session.

LINKGROUP LNKGRP1
     LINK*
ENDLINKGROUP
USSTCP    USSTAB1 LNKGRP1
INTERPTCP INTTAB1 LINK1

Assembled interpret tables used by VTAM® can also be used by Telnet.

If neither a default application nor a USS table is mapped to the connection, the Telnet solicitor screen is sent to the user. For a detailed discussion of the Telnet solicitor, USS table, and INTERPRET table, see Using the Telnet solicitor or USS logon screen.