Documenting FTP client 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® Software Support Center. Documentation is divided into the following categories: essential and helpful (but not essential).

• Essential
  • Precise problem description, including client console, expected results, and actual results
  • Include trace in the output by one of these methods:
    • Coding DEBUG statements in the client's FTP.DATA. See z/OS Communications Server: IP Configuration Reference for information about the DEBUG statement.
    • Invoking the FTP client with the -d or TRACE invocation option. See z/OS Communications Server: IP User's Guide and Commands for information about entering the FTP environment.
    • Specifying a DEBUG subcommand in the client command input stream before the affected transfer. Use this option only if the problem does not involve the initial establishment of the FTP control session.
  • FTP.DATA file used by the client.
    • You can use DEBUG ALL to capture all details possible.
    • When activating the trace, use the DEBUG option TIMESTAMPS to time stamp the client trace output. See z/OS Communications Server: IP User's Guide and Commands for information about the DEBUG subcommand and z/OS Communications Server: IP Configuration Reference for information about the DEBUG statement.
    • If executing the client in batch, collect all the JES output.
• Helpful:
  • Output from the client locstat subcommand
  • Output from the client stat subcommand
  • FTP.DATA data set
  • TCPIP.DATA data set
  • If appropriate, sample data to re-create the problem
  • If the FTP.DATA parameter LOGCLIENTERR is TRUE, report the contents of message EZZ9830I. The message is written to the system log and the job log when the client is running in batch and to the user's terminal during an interactive client session.