FTP connection stops during FILETYPE=JES processing

This problem occurs due to extended periods of inactivity on the control or data connection while the FTP client is waiting for the FTP server to complete the job. Significant delays are possible during FILETYPE=JES processing due to conditions such as heavy system utilization and dispatching priorities.

You can avoid timeouts by using keepalive packets on the control and data connection. You can activate keepalive packets by:
  • Coding the INTERVAL parameter on the TCPCONFIG statement in the TCP/IP profile (PROFILE.TCPIP). See z/OS Communications Server: IP Configuration Reference for more information about the TCPCONFIG statement.
  • Coding the FTPKEEPALIVE statement in FTP.DATA. This activates keep alive packets for the control connection only, and overrides the TCPCONFIG INTERVAL statement. See z/OS Communications Server: IP Configuration Reference for more information about the FTPKEEPALIVE statement.
  • Configuring the DATAKEEPALIVE option to activate keepalive packets for the data connection only. This overrides the TCPCONFIG INTERVAL statement in the stack. You can configure DATAKEEPALIVE by coding a statement in FTP.DATA, by using the site subcommand from the z/OS® FTP client, or by sending a SITE command with the DATAKEEPALIVE parameter to the FTP server. See z/OS Communications Server: IP Configuration Reference for more information about the DATAKEEPALIVE statement.
Parent topic: JES support