Start tracing after FTP initialization

After initialization, you can enable tracing using an MVS™ MODIFY operator command to the FTP server listener process. See Controlling the FTP server traces with MODIFY operator command. Previously established FTP connections are not affected by a MODIFY operator command. Only FTP connections that are established after the MODIFY operator command was issued are subject to tracing.

If you have coded DEBUGONSITE TRUE and DUMPONSITE TRUE in the server's FTP.DATA file, you can use the SITE DEBUG command and the SITE DUMP command, respectively, to change tracing after you log in to FTP. For example, if you want to add JES general tracing and JES extended tracing, enter the following:

SITE DEBUG=(JES) DUMP=(JES)

If you want to restrict the use of the SITE command to change the tracing and your installation has a security product that supports the SERVAUTH class, you can provide additional levels of access control. If the installation has activated the SERVAUTH class and provided a profile for the SITE DEBUG command, only users who have read access to the profile are allowed to use the SITE DEBUG command. The profile name is:

EZB.FTP.systemname.ftpdaemonname.SITE.DEBUG

For example, if the procedure FTPD is used to start the server on system MVS164, the profile name is:

EZB.FTP.MVS164.FTPD1.SITE.DEBUG

The user's SITE DEBUG command is rejected if the security product determines that the user does not have read access to the profile.

If the installation has activated the SERVAUTH class and provided a profile for the SITE DUMP command, only users who have read access to the profile are allowed to use the SITE DUMP command. The profile name is:

EZB.FTP.systemname.ftpdaemonname.SITE.DUMP

For example, if the procedure FTPD is used to start the server on system MVS164, the profile name is:

EZB.FTP.MVS164.FTPD1.SITE.DUMP

The user's SITE DUMP command is rejected if the security product determines that the user does not have read access to the profile.