|
|
|
FTP users accessing an MPE/iX-based FTP server may receive the messages and/or
errors listed below which are based on the Military Standard, FTP,
MIL-STD-1780.
The type of reply is based on the first digit of the number:
- Number
Type - 1nn
Positive preliminary reply - 2nn
Positive completion reply - 3nn
Positive intermediate reply - 4nn
Transient negative reply which user may wish to retry - 5nn
Permanent negative reply
The second digit in the message number represents the following function
groupings (where the first digit x is from 1 to 5 as described above):
- Number
Type - x0n
Syntax errors - x1n
Replies to requests for information (status, help) - x2n
Replies referring to the control and data connections - x3n
Replies for logon process and accounting procedures - x4n
Unspecified - x5n
Status of the server file system
In the following list of messages and errors, the exclamation point (!)
represents a variable value.
| MESSAGE: Data connection already open; transfer starting |
| Level: 125
CAUSE: Data connection has been opened, data transfer has started.
ACTION: None. |
| MESSAGE: File ! opened; data connection will be opened |
| Level: 150
CAUSE: The file requested for a GET, LS or
DIR has been opened.
ACTION: None. |
| MESSAGE: ! command ok. |
| Level: 200
CAUSE: The command was accepted by the server.
ACTION: None. |
| MESSAGE: Type set to !. |
| Level: 200
CAUSE: A TYPE command was received and accepted.
ACTION: None. |
| MESSAGE: Command not implemented at this site. |
| Level: 202
CAUSE: The MPE/iX FTP server received a command that
is not implemented.
ACTION: This command cannot be used. |
| MESSAGE: "!": !. |
| Level: 213
CAUSE: A file status (SIZE | MDTM) command was received and
accepted. This first parameter is the filename. The second contains
detailed information that differs depending on the command.
ACTION: None. |
| MESSAGE: MPE/iX system type. |
| Level: 215
CAUSE: The server received a SYST command.
ACTION: None. |
| MESSAGE: HP ARPA File Transfer Protocol Server [!] (C)
Hewlett-Packard Co. 1990 |
| Level: 220
CAUSE: The server has been started and is ready for user commands.
ACTION: Enter FTP commands. |
| MESSAGE: Server is closing command connection |
| Level: 221
CAUSE: The server received a QUIT command and is
shutting down.
ACTION: None. |
| MESSAGE: Transfer complete. |
| Level: 226
CAUSE: A file transfer for a GET, PUT, LS or
DIR has completed.
ACTION: None. |
| MESSAGE: Data connection is opened with no transfer in
progress. |
| Level: 225
CAUSE: NOT USED
ACTION: None. |
| MESSAGE: Transfer complete. Some records were truncated during
transfer. |
| Level: 226
CAUSE: A data transfer to MPE/iX resulted in some records
being truncated in the target file.
ACTION: It may be necessary to increase the maximum record
size using build parameters. Review the HP ARPA FTP User's
Guide for more information on this subject. |
| MESSAGE: User logged on |
| Level: 230
CAUSE: A USER command was received and accepted. The logon
has succeeded.
ACTION: None. |
| MESSAGE: ! File action successful. |
| Level: 250
CAUSE: A file action for DELE/RMD/XRMD/CWD/XCWD
has competed.
ACTION: None. |
| MESSAGE: ! is the current directory. "!" is the current
session. |
| Level: 257
CAUSE: A PWD command was received and accepted.
ACTION: None. |
| MESSAGE: ! successful, "!" created |
| Level: 257
CAUSE: A directory creation (MKD/XMKD) has completed.
ACTION: None. |
| MESSAGE: Password required for !.
[userpass][,acctpass][,grouppass] |
| Level: 331
CAUSE: A USER command has been received, the server is
waiting for the password.
ACTION: Enter the passwords required. |
| MESSAGE: File exists, ready for destination name. |
| Level: 350
CAUSE: An RNFR (rename from) command has been received, the
server is waiting for a RNTO (rename to). This is part of the user
RENAME command.
ACTION: None. |
| MESSAGE: Data transfer aborted |
| Level: 426
CAUSE: The data connection could not be opened or there
was a network error during the file transfer.
ACTION: Try the transfer again. If this doesn't work try exiting
FTP and connecting again, then transferring the file. If that doesn't work
check for a networking problem
(resources, connection establishment, etc.) on both systems. |
| MESSAGE: '!': Unknown command |
| Level: 500
CAUSE: The MPE/iX FTP server received an unrecognized command.
ACTION: This command cannot be used. |
| MESSAGE: Syntax error in parameter ! |
| Level: 501
CAUSE: One of the parameters in the command was not correct.
The ! will contain the parameter in question.
ACTION: Check the parameter and try again. |
| MESSAGE: ! Command not implemented by this server. |
| Level: 502
CAUSE: The MPE/iX FTP server received a command that
it recognized but has not implemented.
ACTION: This command cannot be used. |
| MESSAGE: Illegal sequence of commands |
| Level: 503
CAUSE: The server was sent a series of commands that
were in the wrong order (example: RNTO before RNFR).
ACTION: Check the commands and send them in the correct
order. |
| MESSAGE: Command not implemented for parameter ! |
| Level: 504
CAUSE: A parameter was specified that is not supported.
For example TYPE EBCDIC is NOT supported by the MPE/iX FTP server.
ACTION: Specify a parameter which is supported. |
| MESSAGE: User log on unsuccessful |
| Level: 530
CAUSE: The server received a user account and/or password
which were not valid.
ACTION: Specify the correct user account and password.
If the user is sure that they are correct, notify the network manager
and have him/her refer to the Installing and Managing
HP ARPA File Transfer Protocol Network Manager's Guide. |
| MESSAGE: Please login with USER and PASS. |
| Level: 530
CAUSE: The user entered a command without being logged
onto the FTP server.
ACTION: Log on with the USER command, then enter the
command again. |
| MESSAGE: File request not taken: ! |
| Level: 550
CAUSE: An MPE/iX File System error was received. The
parameter will contain the text of the specific File System error.
ACTION: Refer to the MPE/iX Error Messages
Manual (Volume 1, 2 and 3). |
| MESSAGE: Illegal file name |
| Level: 553
CAUSE: The file name specified was not a valid MPE/iX file name.
ACTION: Use the correct file name format: either filename
or filename.group.account where each file name part is up to eight
alphanumeric characters, beginning with an alphabetic character. |
|
Complete PDF