FTP Reply Codes
FTP Reply Codesfrom: http://publib.boulder.ibm.com/infocenter/zvm/v5r4/index.jsp?topic=/com.ibm.zvm.v54.kijl0/ftpcod.htm
z/VM V5R4.0 TCP/IP User's Guide
SC24-6127-04
http://publib.boulder.ibm.com/infocenter/zvm/v5r4/topic/com.ibm.zaddinfo.doc/dblue_rule.gif
When you enter an FTP command, TCP/IP displays the sequence of subcommands, if any, that are sent to the foreign host's FTP server. In addition, the subcommand's response is also displayed as a reply code. These replies ensure the synchronization of requests and actions during file transfer, and guarantee that you always know the state of the foreign host's FTP server. The descriptions of the possible reply codes are listed in Table 8.
Note:
In general, the reply code descriptions below will not match the messages received from a foreign host, since reply message text will vary from one server implementation to another. The following descriptions are intended to provide an explanation of the reply codes themselves.
Table 8. FTP Reply CodesCodeDescription110Restart marker reply120Service ready in nnn minutes125Data connection already open; transfer starting150File status okay; about to open data connection200Command okay202Command not implemented; not used on this host211System status, or system help reply212Directory status213File status214Help message215VM is the operating system of this server220Service ready for new user221QUIT command received226Closing data connection; requested file action successful227The FTP server has opened a passive connection for data transfer at the specified IP address and port.230User logged on; requested minidisk, BFS, or SFS Directory not available; proceed234Security data exchange complete250Requested file action or directory okay, completed255In target directory already257PATH NAME created or directory status given331Send password please332Supply minidisk password using account421Service not available; closing Telnet connection425Cannot open data connection426Connection closed; transfer ended abnormally431Temporarily unable to process security450Requested action not taken; file busy, minidisks or SFS directory not available451Requested action aborted; local error in processing452Requested action not taken; insufficient storage space in system500Syntax error; command unrecognized501Syntax error in parameters or arguments502Command not implemented503Bad sequence of commands504Command not implemented for that parameter521Data connection cannot be opened with this PROT setting530Not logged on532Need account for storing files533Command protection level denied for policy reasons534Request denied for policy reasons550Requested action not taken; file not found or no access551Requested action aborted; page type unknown552Requested file action ended abnormally; exceeded storage allocation553Requested action not taken; file name not allowed
页:
[1]