Where to find the FTP client trace

The destination of the z/OS® FTP client trace depends on the environment in which the client executes as described as follows:
  • When the FTP client is invoked interactively from TSO or a REXX exec with an allocated OUTPUT DD, the trace is written to the destination associated with the OUTPUT DD.
  • When the FTP client is invoked interactively from a TSO session with no allocated OUTPUT DD, the trace is written to the user's console.
  • When the FTP client is invoked interactively from OMVS, the trace is written to the user's console, or it can be written to a file by using the OMVS redirect operand (>).
  • When the FTP client is invoked interactively from a REXX exec with no allocated OUTPUT DD, the trace is written to the destination for STDOUT (which might be the user's console).
  • When the FTP client is invoked from any application using the FTP Callable Application Programming Interface (API), the trace output is stored in the interface buffer until the application issues a request to retrieve the output. See z/OS Communications Server: IP Programmer's Guide and Reference for a complete description of the FTP Callable API.
Rules: When the FTP client is invoked from a batch job, the following rules apply:
  • If the client is invoked directly (EXEC PGM=FTP), the trace is written to the destination associated with the OUTPUT DD.
  • If the client is invoked from TSO in batch (EXEC PGM=IKJEFT01), the trace is written to the destination associated with the OUTPUT DD if one exists. Otherwise, the trace is written to the destination associated with the SYSTSPRT DD.
  • If the client is invoked from a REXX exec in batch, whether under batch TSO, the trace is written to the destination for the OUTPUT DD (if one exists). Otherwise, the trace is written to the destination for STDOUT (under batch TSO, this might be the SYSTSPRT DD).
Parent topic: FTP client