This can be done by issuing the following FTP subcommand before starting the failing data transfer:ģ. Obtain an z/OS FTP client trace with options BAS, TIM, and FLO. If this is a high-volume system, be sure to reference section 6 on how to filter tracing based on IP addresses and ports.Ģ. Detailed instructions for doing this can be found in How to Collect PKTTRACE and CTRACE on z/OS. Before retrying the failing data transfer, start the packet trace facility. Steps for resolving FTP timeouts during data transfer for the client :ġ. Here are instructions on how to do this:ģ.2 Change (comment out) the following line: If you have a checkpoint firewall, make sure you have turned off the FTP enforce new line setting in the firewall's configuration. Make sure your FTP KEEPALIVE option has a value of 60 seconds or greater.ģ. If you need assistance identifying which FTP.DATA the FTP server is using, the hierarchical search order can be found in the section on TCP/IP configuration data sets in the IP Configuration Reference manual.Ģ. Be sure the following z/OS FTP client timer (specified in the client FTP.DATA file) default values are set to the defaults or higher. Many times this results in the z/OS FTP server issuing messages EZA2590E and EDC8121I (connection reset), EZA2589e (connection interrupted or timed out), or EZA1721W (server not responding)ġ.
FTP timeouts can occur during data transfer for the z/OS FTP client.
0 kommentar(er)
