Author: Robert Sample
Posted: Sun Jan 22, 2017 6:52 pm (GMT 5.5)
Are both sides of the connection using EBCDIC? If so, use the TYPE E FTP subcommand to meet the requirement of the EZA2501W error message. If the other end is NOT a z/OS system, you may discover significant issues with attempting to use the RESTART subcommand -- as in the server may not even support it. I've been using FTP on z/OS and its predecessors for more than 25 years, and I've NEVER had any need to use the RESTART subcommand. You should confirm with your site support group that the required FTP.DATA parameters are set appropriately; you've got to get the LOCSITE / SITE parameters correct, and you may have to experiment with the FTP subcommands (such as MODE) before you can successfully use RESTART.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Sun Jan 22, 2017 6:52 pm (GMT 5.5)
Are both sides of the connection using EBCDIC? If so, use the TYPE E FTP subcommand to meet the requirement of the EZA2501W error message. If the other end is NOT a z/OS system, you may discover significant issues with attempting to use the RESTART subcommand -- as in the server may not even support it. I've been using FTP on z/OS and its predecessors for more than 25 years, and I've NEVER had any need to use the RESTART subcommand. You should confirm with your site support group that the required FTP.DATA parameters are set appropriately; you've got to get the LOCSITE / SITE parameters correct, and you may have to experiment with the FTP subcommands (such as MODE) before you can successfully use RESTART.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
