Ftp Return Code 10000 Error Code 00010
topic Author Message viniIntermediateJoined: 12 Jan 2004Posts: 231Topics: 46Location: Maryland Posted: Mon Jan 19, 2004 11:07 am Post subject: FTP
Ftp Std Return Code = 10000 Error Code = 00008
Issue Hi , When I try to FTP a Data Set recv error from getnextreply - edc8128i connection refused thru a PC Software like Core lite and for same IP Address and DS it works fine.
Mainframe Ftp Error Code = 00008
However , when I try to do same thru a JCL ...it fails saying 'Host cannot be reached' !!! Anyone faced this problem before or is aware of why eza1735i std return code = 16550, error code = 00002 and how to fix this issue ??? The Messages in SYSPRINT are as follows : EZA1450I IBM FTP CS V2R10 EZA1466I FTP: using ATCPIP EZA1772I FTP: EXIT has been set. EZA1456I Connect to ? EZA1736I 172.20.8.1 EZA1554I Connecting to: 172.20.8.1 port: 21. EZA2590E getNextReply error from recv = (1130.74500446) - EDC8130I EDC8130I Host cannot be reached. EZA1475I Connection eza2590e recv error from getnextreply - edc8128i connection refused. (errno2=0x769f0442) with 172.20.8.1 terminated EZA1735I FTP Return Code = 10000, Error Code = 00010 The JCL Step : //S5 EXEC PGM=FTP,PARM='(EXIT' //INPUT DD * 172.20.2.1 UIVS013 GREASE ASCII PUT WLFA.ASX810FA.OUT.SEQ WLFA.ASX810FA.OUT.SEQ QUIT //SYSPRINT DD SYSOUT=* //SYSOUT DD SYSOUT=* // Vini. Back to top Mike ChantreyIntermediateJoined: 10 Sep 2003Posts: 234Topics: 1Location: Wansford Posted: Mon Jan 19, 2004 11:17 am Post subject: "Host cannot be reached" FTPing from the mainframe - sounds like a possible firewall issue to me, if you can send to the same IP address from your PC. Or is it an IP address error? Your error messsage says 172.20.8.1 but your FTP input says 172.20.2.1 If it is the firewall you will need to find out who administers this firewall. Your m/f sysprogs should at least be able to point you in the right direction even if they don't handle this themselves. Try pinging this IP from TSO command prompt: PING 172.20.2.1 or PING 172.20.8.1 (whichever is the correct version) If you still can't reach it, this supports the 'fir
good, bad or incomplete: Range Purpose 1xx Positive Preliminary reply The requested action is being initiated; expect another reply before proceeding with a new https://en.wikipedia.org/wiki/List_of_FTP_server_return_codes command. (The user-process sending another command before the completion reply would be in violation of protocol; but server-FTP processes should queue any commands that arrive while a preceding command is in progress.) This type of reply can be used to indicate that the command was accepted and the user-process may now pay attention to the data connections, for implementations where simultaneous error code monitoring is difficult. The server-FTP process may send at most, one 1xx reply per command. 2xx Positive Completion reply The requested action has been successfully completed. A new request may be initiated. 3xx Positive Intermediate reply The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information. The user should send another command std return code specifying this information. This reply is used in command sequence groups. 4xx Transient Negative Completion reply The command was not accepted and the requested action did not take place, but the error condition is temporary and the action may be requested again. The user should return to the beginning of the command sequence, if any. It is difficult to assign a meaning to "transient", particularly when two distinct sites (Server- and User-processes) have to agree on the interpretation. Each reply in the 4xx category might have a slightly different time value, but the intent is that the user-process is encouraged to try again. A rule of thumb in determining if a reply fits into the 4xx or the 5xx (Permanent Negative) category is that replies are 4xx if the commands can be repeated without any change in command form or in properties of the User or Server (e.g., the command is spelled the same with the same arguments used; the user does not change his file access or user name; the server does not put up a new implementation.) 5xx Permanent Ne