Troubleshooting
Problem
Batch jobs that run the FTP client program have the commands rejected. The commands appear to be correct.
Symptom
Some common examples of this problem are:
EZA1460I Command:
EZA1736I PUT MYFILE.INPUT REMOTE.FILE
EZA1542I Usage: PUT localfile <foreignname>
EZA1460I Command:
EZA1736I OPEN FTP.COMPANY.COM
EZA1553E INVALID PORT NUMBER. OPEN FAILS.
Cause
Messages like this are normally the result of invalid FTP subcommand syntax, make sure that the commands are specified as shown in the IP User's Guide and Commands manual section on FTP Subcommands. Otherwise check the JCL data set (or the data set referenced by the INPUT DD) for sequence numbers. The FTP command does not filter out the sequence number fields in its input, so these will be treated as another value specified on the command.
In the examples shown above:
- The PUT command was rejected due to a third value (after the remote file name specification).
- The OPEN command was rejected because the third value is greater than 65535.
Resolving The Problem
To correct this condition, go into ISPF EDIT on the affected data set and use the UNNUMBER command to remove the line numbering. Then SAVE and resubmit the job.
An alternative change would be to terminate each line (including those with the plus (+) continuation character) with a semi-colon (;). This is the syntax used to represent the start of a comment, and the rest of the line (including any sequence numbers) is ignored.
For z/OS 1.9 and above, the SEQNUMSUPPORT TRUE statement can be specified in the FTP.DATA input used for FTP clients. This will cause the sequence number fields of the command inputs to be ignored, which will avoid this problem.
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21139161