Isolating Problems

To expedite the diagnostics process, prepare the following information for the IBM® Support representative:

  • Version, release, maintenance level, and operating system for the IBM Connect:Direct® products being used on both nodes, for example, Connect:Direct for z/OS® 6.0 with Connect:Direct for HP NonStop 3.4.00.
  • Release levels of the operating system, VTAM, and other software involved
  • Details describing the complete scenario, including:
    • Commands that are issued, with exact syntax and order
    • Files or devices that are involved. Note the file contents and the type of file (such as DCB file attributes, GDG, Tape, SMS, striped, compressed)
    • Interface that you used, such as batch interface, IUI, or operator interface
    • Error messages for both nodes
    • System logs for both nodes, including any messages generated while the problem occurred. Check the SYSLOG for Connect:Direct for z/OS nodes
    • Which side is PNODE/SNODE
    • The direction of the data transfer
    • What connection protocol you are using (LU0, LU6.2, IBM TCP/IP, TCPAccess)
    • If the node is a IBM Connect:Direct/Plex or stand alone server
    • IBM Connect:Direct Process including the FILE attributes for the FROM and TO files for both nodes
    • I/O device types
    • Network map information
    • Statistics information for both nodes including ALLOC information
Note: Be prepared to recreate the problem. Problem recreation is your responsibility.

Supporting Documentation

Problem determination can be involved and can require extensive research. We ask you to gather some of the following supporting documentation to help analyze the problem. Not all of this information is applicable to all problems or all operating environments.

  • IBM Connect:Direct statistics for both nodes
  • RPLERRCK output
  • ESTAE output
  • VTAM definitions
  • APPLID definitions
  • Logmode table entry
  • Class of Service (COS) entry
  • D NET VTAM display
  • IBM Connect:Direct traces
  • Network map information

You can use your network management software or VTAM commands to isolate any session-related problems.

Diagnostic Rexx Exec for IUI Environments

If you are experiencing problems with the IBM Connect:Direct IUI, you can use the DGA#CAP Rexx exec available in the SDGAISPC target library to facilitate diagnosis of IUI problems.

To invoke the DGA#CAP Rexx exec, type the following TSO command:
The exec issues an ISPF long message containing the dataset name where the output is written. Contact IBM Support and give the Support representative the output generated by the DGA#CAP Rexx exec.