DEBUG (Create Client Trace and Control Display of Server Subcommands Sent to Remote System)

Note: Only use the FTP client trace to report software problems to IBM®. System performance might be affected by this function.

You can use this capability in OS/400® V4R4 and later of the operating system.

FTP client subcommand

To produce an FTP client trace or display, use the DEBUG FTP client subcommand. The DEBUG subcommand toggles the debugging mode. If the client specifies an optional debug-value, it will use it to set the debugging level. When debugging is on, the client displays with the string '>>>'. You must set the debug-value 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 you don't specify a value, the debug value toggles from zero to one or from a positive integer to zero.
100
Initiate an FTP client trace. The client continues running the trace until the DEBUG is off or until the server ends the FTP client. When the server ends the trace, there might be a significant delay while it formats the trace data.

To initiate a trace immediately when the FTP client starts, you need to create the QTMFTPD100 data area in the QTEMP library by using this command:

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

If the QTMFTPD100 data area exists, then it will set the debug value to 100 and start an FTP client trace. The purpose of this capability is to enable the FTP client debug traces in those situations when an FTP client trace cannot start with the DEBUG 100 subcommand.

Related reference
File Transfer Protocol client syntax conventions