FTP Error Codes

The ftp utility issues an error, or reply, code to every user command. For reference, in case your ftp session generates an error, here are the meanings of the reply codes.

CodeDescription
100 Series CodesThe requested action is being initiated, expect another reply before proceeding with a new command.
110Restart marker reply.
120Service ready in nnn minutes.
125Data connection already open, transfer starting.
150File status okay, about to open data connection.
200 Series CodesThe requested action has been successfully completed.
200Command okay.
202Command not implemented, superfluous at this site.
211System status, or system help reply.
212Directory status.
213File status.
214Help message.
215NAME system type. (Where NAME is an official system name from the list in the Assigned Numbers document.)
220Service ready for new user.
221Service closing control connection. Logged out if appropriate.
225Data connection open; no transfer in progress.
226Closing data connection. Requested file action successful (for example, file transfer or file abort).
227Entering Passive Mode
230User logged in, proceed.
250Requested file action okay, completed.
257"PATHNAME" created.
300 Series Codes The command has been accepted, but the requested action is being held in abeyance, pending receipt of further information.
331User name okay, need password.
332 Need account for login.
350Requested file action pending further information.
400 Series CodesThe 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.
421Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.
425Can't open data connection.
426Connection closed; transfer aborted.
450Requested file action not taken. File unavailable (e.g., file busy).
451 Requested action aborted: local error in processing.
452Requested action not taken. Insufficient storage space in system.
500 Series Codes The command was not accepted and the requested action did not take place.
500Syntax error, command unrecognized. This may include errors such as command line too long.
501Syntax error in parameters or arguments.
502Command not implemented.
503Bad sequence of commands.
504Command not implemented for that parameter.
530Not logged in.
532Need account for storing files.
550Requested action not taken. File unavailable (e.g., file not found, no access).
552Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
553Requested action not taken. File name not allowed.