Documenting server problems

If the problem is not caused by any of the common errors described in this section, collect the following documentation before calling the IBM® Support Center.

Documentation is divided into the following categories: essential and helpful (but not essential).
  • Essential
    • Precise description of problem, including expected results and actual results
    • z/OS UNIX FTP server dump (for abends)
    • z/OS UNIX FTP server traces (see Diagnosing FTP server problems with traces for information about collecting FTP server traces)
      • Minimum for initial problem reporting: DEBUG BAS
  • Helpful
    • FTP client output
      • If the FTP client is a z/OS® client, include a trace in the output by one of these methods:
    • Server FTP.DATA data set
    • TCPIP.DATA data set
    • PROFILE.TCPIP data set
    • ETC.SERVICES data set
    • The reply from the STAT or XSTA command issued to the server.
      Guidelines:
      • Issue the STATus subcommand from the z/OS FTP client to retrieve STAT command output from the server. From non z/OS clients, you may have to issue QUOTE STAT to retrieve the output from the server.
      • Issue the STATus subcommand with a parameter from the z/OS FTP client to issue the XSTA command to the server. The XSTA command retrieves output related to that parameter only. From z/OS clients prior to V1R8, or from non-z/OS clients, issue QUOTE XSTA (parameter to retrieve the output from the server.
    • Any console messages issued for resources experiencing errors.
    • If applicable, sample data to re-create the problem