z/OS Communications Server: IP Diagnosis Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Steps for analyzing hangs

z/OS Communications Server: IP Diagnosis Guide
GC27-3652-02

Determine what is hung and what documentation to collect.

Procedure

Perform the following steps to analyze and collect documentation:

  1. Determine whether all TCP/IP processing stopped or only processing with respect to a single device, or something in between. Also determine what, if any, recovery action was taken by the operator or user at the time the hang was encountered. Some information about the activity that immediately preceded the hang might be available on the system log or in application program transaction logs.
  2. Determine whether TCP/IP responds to commands, such as Ping or Netstat HOME/-h. If TCP/IP does not respond to these commands, take an SVC dump of TCP/IP address space and contact the IBM® Software Support Center. If TCP/IP does respond to the commands, it is not hung.
  3. Determine whether a particular application (such as z/OS UNIX FTP or a user-written application) is hung.

    Take a dump of the OMVS address space, the TCP/IP address space, and the application address space.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014