Quick checklist for common problems

The following list summarizes some initial checks that can be made quickly.

Use the following checklist to identify problem areas:
  1. Is the TCP/IP SNALINK LU6.2 network active?

    PING the remote TCP/IP host from the local TCP/IP host to verify that the SNALINK LU6.2 network is active. If the SNALINK LU6.2 network is not active, continue through this list to identify the problem.

    If the PING still fails after working through this list, see Network connection establishment problems for a detailed list of network connection problems and their solutions.

  2. Have you completed all the required definitions?

    See Steps for setting up a SNALINK LU6.2 network for the list of definitions and configurations required. Continue through this list if connection problems persist.

  3. Have the VTAM major node and application LU used by the SNALINK LU6.2 address space been varied active?

    See Useful VTAM operations for details on how to use the VTAM® DISPLAY command to identify the status of the VTAM major node and application LU.

    If the VTAM application LU is not in a CONCT state, see Useful VTAM operations for details about how to vary the VTAM application LU active.

  4. Are the TCP/IP and SNALINK LU6.2 devices started and active on the local and remote host?

    Check to see whether the TCP/IP and SNALINK LU6.2 devices are active and running. The MVS™ SDSF facility can be used to view the active address space list for MVS hosts.

    If the SNALINK LU6.2 address space does not start, see Problems starting the SNALINK LU6.2 address space for a detailed list of startup problems and their solutions.

  5. Did the SNALINK LU6.2 address space list any configuration errors to the SYSPRINT data set?

    Use the JCL DD statement in the SNALINK LU6.2 cataloged procedure to identify the destination of the SYSPRINT output and check for errors. If errors occur, see Finding error message documentation to determine the reason for the configuration errors. Text in the message documentation specifies the action required to fix the problem.

  6. Have the TCP/IP-to-SNALINK LU6.2 DLC connections been established?

    See Using NETSTAT for details about how to use the NETSTAT command to identify the status of the DLC connection.

    If the status of the DLC connection is not “Connected,” see DLC connection problems for a detailed list of SNALINK LU6.2 DLC connection problems and their solutions.

  7. Does the MVS system console contain VTAM error messages?

    See z/OS Communications Server: SNA Messages and z/OS Communications Server: IP and SNA Codes for detailed descriptions of the VTAM error messages and sense codes. These messages might indicate a network configuration or hardware error.

Parent topic: Diagnosing problems