z/OS Communications Server
Tracing the FTP Client


The FTP client has multiple trace points which can be set to trace a variety of events during the course of the FTP session, and can be activated dynamically or at FTP initialization. These different points are as follows:


TRACING THE FTP CLIENT AT STARTUP

Three methods currently exist to activate the FTP client trace at client initiation:

The '-d' or '(TRACE' flag can be used interchangibly as they invoke the same options:
   CMD INT FSC(1) SOC(1)

To invoke additional options at FTP client startup, the FTP.DATA file used by the client must contain DEBUG statement(s) specifying which options are to be activated. These can be activated on multiple lines:
   DEBUG ACC
   DEBUG PAR
   DEBUG SEC

or on a single line:
   DEBUG ACC PAR SEC


TRACING THE FTP CLIENT DYNAMICALLY

If desired, FTP tracing can be activated dynamically following FTP startup using the DEBUG subcommand. Multiple options can be specified on a single command or on multiple commands. Note that specification of options is cumulative until DEBUG NONE is specified to toggle off the tracing. Examples of this are illustrated in the following client output:
   EZA1460I Command:
  Debug ACC INT FSC
   EZA2923I Active client traces - INT ACC FSC(1)
   EZA1460I Command:
  Debug SOC UTL
   EZA2923I Active client traces - INT ACC UTL FSC(1) SOC(1)
   EZA1460I Command:
  Debug NONE
   CL0188 debug: entered
   GU2815 setDebug: entered
   EZA2923I Active client traces - NONE
   EZA1460I Command:

Also note that the DEBUG command can be used to toggle on and off a trace consisting of codepoints
   CMD INT FSC(1) SOC(1)

This is illustrated by the following client output:
   EZA1460I Command:
  debug
   EZA2923I Active client traces - CMD INT FSC(1) SOC(1)
   EZA1460I Command:
  debug
   PC0324 parseCmd: subcommand: debug
   EZA2923I Active client traces - NONE
   EZA1460I Command: