Analysis

Table 1 lists some of the common DLC connection problems between the SNALINK LU6.2 address space and the TCP/IP address space.

Table 1. Common DLC connection problems
If this is displayed. . . Then this might have occurred . . . Resolution
The message Error in DLC connect... has been displayed on the MVS™ system console and the NETSTAT DEVLINKS output shows that the DLC connection status is either Issued Connect or Will retry connect. The TCP/IP address space is attempting to attach to the SNALINK LU6.2 address space, but the SNALINK LU6.2 address space is not responding. Check whether the SNALINK LU6.2 address space is active and start it, if necessary.
The SNALINK LU6.2 address space has started, but the Link open message has not been displayed on the MVS system console, no other error messages have been displayed on the console, and the NETSTAT DEVLINKS output shows that the DLC connection status is either Issued Connect or Will retry connect. This problem can be due to one of the following situations:
  1. The SNALINK LU6.2 address space might be rejecting the connect attempt from the TCP/IP address space because it has the wrong TCP/IP ID.
  2. The SNALINK LU6.2 address space might be rejecting the connect attempt from the TCP/IP address space because of a SNALINK LU6.2 link name that is incorrectly defined.
  • Check the SNALINK LU6.2 SYSPRINT output for the “Rejecting DLC path for the link_name, wrong TCP/IP id tcpip_addr_space” error message.If this error message is displayed, check whether a valid TCPIP.DATA data set was specified as the SYSTCPD ddname in the SNALINK LU6.2 cataloged procedure and correct it, if necessary.
    Note: SYSTCPD can be overridden by the global TCPIP.DATA file.

    See z/OS Communications Server: IP Configuration Reference for an example of a SNALINK LU6.2 cataloged procedure and for the search order for the TCPIP.DATA data set.

    If a valid TCPIP.DATA data set has been used, check the TCP/IP address space specified in the TCPIPJOBNAME statement within it.

    See z/OS Communications Server: IP Configuration Reference for a detailed description of the TCPIPJOBNAME statement in the TCPIP.DATA.

  • Check the SNALINK LU6.2 SYSPRINT output for the “Rejecting DLC path for link_name, not configured” error message.

    If this error message is displayed, check to see whether the link name specified in the LINK statement of the SNALINK LU6.2 configuration data set matches the link name specified in the LINK statement associated with the SNALINK LU6.2 device defined in hlq.PROFILE.TCPIP.

    See z/OS Communications Server: IP Configuration Reference for details about the SNALINK LU6.2 LINK statement syntax and the TCPIP LINK statement syntax.
The SNALINK LU6.2 address space has been started but the Link opened message has not been displayed and the NETSTAT DEVLINKS output shows that the DLC connection is Inactive. The DLC connection to the SNALINK LU6.2 device associated with the SNALINK LU6.2 address space might not have been started by the TCP/IP address space. Check the START statements in hlq.PROFILE.TCPIP.

If the SNALINK LU6.2 device has not been started, use the VARY TCPIP,procname,START,device_name for the SNALINK LU6.2 device or include the START statement in the hlq.PROFILE.TCPIP and restart the TCP/IP address space.

See z/OS Communications Server: IP Configuration Reference for a detailed description of the START statement in the hlq.PROFILE.TCPIP.
Parent topic: DLC connection problems