Tracing the FTP client

To produce an FTP client trace or display the subcommands sent to the FTP server, use the DEBUG FTP client subcommand.

The DEBUG subcommand toggles the debugging mode. If an optional debug-value is specified, it is used to set the debugging level. When debugging is on, each subcommand sent to the FTP server is displayed and preceded by the string '>>>'. The debug-value must be set to 100 to produce an FTP client trace.

DEBug [debug value]

debug value: If the debug-value is 0, debugging is off. If the debug-value is a positive integer, debugging is on.
If no value is specified, the debug-value is toggled from zero to one or from a positive integer to zero.
100: Initiate an FTP client trace. The client continues running the trace until DEBUG is turned off or until the FTP client is ended. (When the trace is ended, there might be a significant delay while the trace data is formatted.)

The FTP client trace should only be used for reporting software problems to IBM. System performance can be adversely affected by this function.

A new capability has been added to the FTP client for debugging for V4R4. This function is similar to the DEBUG 100 described above. When the client is started, it first checks for the existence of a data area named QTMFTPD100.

You need to create the dataarea QTMFTPD100 in the QTEMP library using this command:

     CRTDTAARA DTAARA(QTEMP/QTMFTPD100) TYPE(*LGL)AUT(*USE)

If the QTMFTPD100 dataarea exists, then it will set the debug value to 100 and start an FTP client trace. The purpose of this capability is to enable FTP client debug traces to be done in those situations when an FTP client trace cannot be started by issuing the DEBUG 100 subcommand.

Parent topic:

Troubleshooting File Transfer Protocol

Related concepts
Materials required for reporting FTP problems