z/OS Communications Server: IP Programmer's Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


FTP client API for REXX trace

z/OS Communications Server: IP Programmer's Guide and Reference
SC27-3659-02

The FTP client API for REXX trace is used to debug problems in the FTP client API for REXX function package. The interface cannot be used to debug errors in the trace itself or any error that prevents the interface from accessing the trace data set. The trace writes records for requests to the interface and the results of interface requests.

Tip: The FTP client API for REXX trace is separate from the FTP client API trace. It uses a different output file and has a different enabling mechanism. The FTP client API for REXX trace is used to debug problems in the FTP client API for REXX function package, while the FTP client API trace is used to debug problems in the underlying EZAFTPKS interface and record activity and data that are returned to the interface that might not otherwise be available to the application.

The FTP client API for REXX trace is activated by specifying the z/OS® UNIX FTP_REXX_TRACE_FILE environment variable or allocating the FTPRXTRC DD name. The FTP client API for REXX first looks for the FTP_REXX_TRACE_FILE environment variable (z/OS UNIX environment only) and then for the FTPRXTRC DD allocation.

The FTP client API for REXX trace can be written to any of the following:
  • JES SYSOUT
  • An MVS™ sequential data set (a member of a PDS is not supported); the data set must already exist or be allocated as new with DCB characteristics of an LRECL value in the range 80 – 256 and a RECFM value of Fixed Block
  • A z/OS UNIX file. The file can be either an existing file or a file dynamically allocated by the FTP client API for REXX when needed
Restriction: In order for the FTP client API for REXX to be able to write trace records, the output data set or file must meet the following conditions:
  • The data set or file must be a fixed block data set.
  • For an MVS data set, the record format must be fixed.
  • The data set or file record length must be in the range 8 – 256 bytes.
  • The data set or file block size must be a multiple of the record length.
  • The data set or file must not be block mode.
Data sets and files created by the FTP client API for REXX meet these conditions by default. If a file or data set is created by some other means, then you must ensure these conditions are met or no trace records will be written.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014