Configuring statically defined LU 6.1 ISC terminals to use TCP/IP

Configuring a statically defined ISC terminal to use TCP/IP requires a cold start of IMS, updates to stage 1 system definition macros, and the DFSDCxxx PROCLIB member.

By default, statically defined ISC terminals use VTAM® for communication. The ISCTCPIP parameter in the DFSDCxxx PROCLIB member enables TCP/IP for statically defined ISC terminals.

Requirements: To support TCP/IP, ISC must be defined to support parallel sessions. ISC TCP/IP communications does not support single-session ISC terminals.

Statically defined ISC terminals must specify UNITYPE=LUTYPE6 in the TYPE stage-1 system definition macro.

To configure a statically defined LU 6.1 ISC terminal to use TCP/IP:

Procedure

  1. If you are switching an existing terminal from VTAM to TCP/IP, ensure that UNITTYPE=LUTYPE6 is specified on the TYPE macro of the system definition macros that define the terminal.
    If UNITTYPE=LUTYPE6 is not specified, an error message will be issued when the ISCTCPIP parameter is processed in the DFSDCxxx member and TCP/IP will not be enabled for the terminal.
  2. If you are defining a new terminal, define the terminal by coding the appropriate system definition macros.
    The TYPE macro must specify UNITYPE=LUTYPE6 and parallel session must be defined by coding the VTAMPOOL and SUBPOOL macros. For example:
    TYPE  UNITYPE=LUTYPE6
    TERMINAL  NAME=LU6NDPA,MSGDEL=SYSINFO,EDIT=(NO,NO),     X
    SESSION=3,OPTIONS=NOMTOMSG,                             X
    COMPT1=(SINGLE1,VLVB),                                  X
    COMPT2=(SINGLE2,VLVB),                                  X
    COMPT3=MULT1   
    VTAMPOOL                                   
         SUBPOOL  NAME=LU6SPA,MSGDEL=SYSINFO   
            NAME  LU6LTPA1,COMPT=2,ICOMPT=1  
         SUBPOOL  NAME=LU6SPB 
            NAME  LU6LTPB1 
         SUBPOOL  NAME=LU6SPC 
            NAME  LU6LTPC1 

    If UNITTYPE=LUTYPE6 is not specified, when the ISCTCPIP parameter is processed in the DFSDCxxx member, IMS will issue an error message and TCP/IP will not be enabled for the terminal.

  3. In the DFSDCxxx PROCLIB member, define the terminal to use TCP/IP communications by specifying the name of the terminal and the name of IMS Connect instance that provides TCP/IP support on the ISCTCPIP keyword, as in the following example: ISCTCPIP=(LU6NDPA,ICON1)
  4. Cold start IMS.

    IMS does not read changes to the ISCTCPIP keyword during warm or emergency restarts.