FTP User Messages and Errors

CAUSE: The User-FTP program encountered an error while trying to load the FTP command keywords onto its program stack from the FTP catalog. This probably indicates an internal FTP error.

ACTION: Check the permissions on the file FTPC000.ARPA.SYS. The security for READ must be set to ANY. If the permissions are correct, note the circumstances and contact your Hewlett-Packard representative for assistance.

CAUSE: The user entered an FTP command which exceeded 255 characters.

ACTION: Try entering the command using fewer characters.

CAUSE: An invalid or unknown command was issued to the User-FTP program.

ACTION: Check the command for spelling. Use the help command for a list of supported HP ARPA FTP commands.

CAUSE: An FTP command was entered which requires a host connection and no connection was established.

ACTION: Open a host connection using the OPEN command and try the command again.

CAUSE: FTP was unable to open a host connection. Typically this FTP error is accompanied by a socket error which provides more information.

ACTION: Check the spelling of the host name or IP address. Otherwise, seek the assistance of your Node Manager.

CAUSE: An FTP command was entered with invalid parameter syntax.

ACTION: Check the syntax of the desired command.

CAUSE: An erroneous reply code was returned from the remote server for some FTP command.

ACTION: Enable debug and verbose and try the operation again.

CAUSE: An error was detected during a data transfer. This error is accompanied by another error which indicates the problem.

ACTION: Use the accompanying error to resolve the problem.

CAUSE: The MPE/iX target file could not be opened. This error is typically accompanied by a file system error.

ACTION: Use the accompanying file system error to resolve the problem.

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.

CAUSE: A data transfer to an MPE/iX target file did not have enough records to hold the data from the source file.

ACTION: It may be necessary to increase the maximum number of records in the target file by using build parameters. Review the HP ARPA File Transfer Protocol User's Guide for more information on this subject.

CAUSE: A data transfer (in APPEnd mode) to an MPE/iX target file, did not have enough records to hold the extra data from the source file.

ACTION: Copy the target file to a new file with a larger limit and append to the new file.

CAUSE: The FTP MODE command was entered.

ACTION: None.

CAUSE: The FTP STRUCT command was entered.

ACTION: None.

CAUSE: The FTP FORM command was entered.

ACTION: None.

CAUSE: The FTP VERBOSE command was entered when verbose was enabled.

ACTION: None.

CAUSE: The FTP VERBOSE command was entered when verbose was disabled.

ACTION: None.

CAUSE: The FTP DEBUG command was entered when debug was enabled.

ACTION: None.

CAUSE: The FTP DEBUG command was entered when debug was disabled.

ACTION: None.

CAUSE: The FTP TYPE command was entered without any parameters while in ASCII mode.

ACTION: None.

CAUSE: The FTP TYPE command was entered without any parameters while in binary mode.

ACTION: None.

CAUSE: The user entered the FTP OPEN command during an opened session.

ACTION: Enter the USER command to logon, or the CLOSE command before opening another connection.

CAUSE: An unknown error was detected from some underlying subsystem.

ACTION: Seek the assistance of your Hewlett-Packard representative for assistance.

CAUSE: The user specified a BUILD command parameter for record type that was not Fixed or Variable.

ACTION: Only fixed and variable record format is supported. Refer to the HP ARPA File Transfer Protocol User's Guide for assistance.

CAUSE: The user specified a build parameter for a file type that is not of type Standard (STD).

ACTION: Only the STD file type is supported. Refer to the HP ARPA File Transfer Protocol User's Guide for assistance.

CAUSE: The user attempted to use a file equate during a file transfer.

ACTION: File equates are not yet supported. Try the transfer again without using file equates.

CAUSE: The FTP user did not receive a required reply from an FTP server in the allocated time window.

ACTION: Close the connection and quit before trying again. Try to ping the remote system using PING.NET.SYS. If this does not succeed, no FTP connection can be established. Follow the troubleshooting instructions in the Installing and Managing HP ARPA File Transfer Protocol Network Manager's Guide.

CAUSE: The EXITONERROR command was entered while the exit-on-error feature was disabled.

ACTION: None.

CAUSE: The EXITONERROR command was entered while the exit-on-error feature was enabled.

ACTION: None.

CAUSE: An invalid IP address was used while trying to open a connection.

ACTION: Refer to the HP ARPA File Transfer Protocol User's Guide for assistance.

CAUSE: An ASCII data transfer occurred to an MPE/iX binary file.

ACTION: If the intent was to transfer binary data, then use the BINARY command to change transfer mode to binary. If the intent was to transfer ASCII data, then specify an MPE/iX ASCII file using the appropriate MPE/iX BUILD parameter. Refer to the HP ARPA File Transfer Protocol User's Guide for further assistance.

CAUSE: An ASCII data transfer occurred to an MPE/iX binary file.

ACTION: If intent was to transfer ASCII data, then use the ASCII command to change transfer mode to ASCII. If the intent was to transfer binary data, then specify an MPE/iX binary file using the appropriate MPE/iX BUILD parameter. Refer to the HP ARPA File Transfer Protocol User's Guide for further assistance.

CAUSE: Internal Error. An I/O completion was received for an unknown file number during the attempted establishment of a data connection.

ACTION: Note the circumstances and seek the assistance of your Hewlett-Packard representative.

CAUSE: A non-unique command string was entered at the ftp> prompt.

ACTION: Check the command spelling and try again.

CAUSE: A connection request to a remote FTP server was accepted.

ACTION: None.

CAUSE: The PROMPT command was issued while prompting was disabled.

ACTION: None.

CAUSE: The PROMPT command was issued while prompting was enabled.

ACTION: None.

CAUSE: The CASE command was issued while "Forcing Lower Case" was disabled.

ACTION: None.

CAUSE: The CASE command was issued while "Forcing Lower Case" was enabled.

ACTION: None.

CAUSE: The file is already being accessed exclusively by the system or by another user.

ACTION: If the file is being accessed by the system, there is nothing you can do. If the file is being accessed by another user, try again later.

CAUSE: The filename specified is longer than the maximum allowed by MPE/XL: "FILENAME/LOCKWORD.GROUPNAM.ACCTNAME". This error is typically caused by trying to copy a file from a machine running an operating system which allows longer file names. For example, "GET /user/local/lib/.../ remotefile"

ACTION: Specify a target file name. The correct syntax for the above example would be "GET /user/local/lib.../ remotefile localfile".

CAUSE: The indirect file name specified in the mput command was not found: "mput ^filename".

ACTION: Make sure the indirect file exists.

CAUSE: The directory specified does not exist or is not accessible.

ACTION: Check to see if the directory exists and if so, what its access rights are.

CAUSE: User entered "TIMEOUT [num-secs]"

ACTION: If num-secs was specified, the connection time-out value was set. Otherwise, the current value was simply displayed.

Note: a value of 0 indicates no time-outs.

CAUSE: The FTP sunique command was entered when store-unique was disabled.

ACTION: Subsequent put commands will guarantee that the file will be created with a unique name on the remote machine.

CAUSE: The FTP sunique command was entered when store-unique was enabled.

ACTION: None.

CAUSE: The FTP runique command was entered when receive-unique was disabled.

ACTION: Subsequent get commands will guarantee that the file will be created with a unique name on the local machine.

CAUSE: The FTP runique command was entered when receive-unique was enabled.

ACTION: None.

CAUSE: The FTP trace command was entered when command tracing was disabled.

ACTION: When an FTP connection to a remote system is established, TCP tracing will be turned on. If a connection already exists, tracing will be turned on now.

CAUSE: The FTP trace command was entered when command tracing was enabled.

ACTION: If an FTP connection exists to a remote system and tracing is enabled, it will be turned off.

CAUSE: The FTP trace command was entered when data tracing was disabled.

ACTION: When a connection for a data transfer is established, TCP tracing will be turned on.

CAUSE: The FTP trace command was entered when data tracing was enabled.

ACTION: None.

CAUSE: Command tracing was turned on and a connection to a remote system was established.

ACTION: Use this file for debugging purposes.

CAUSE: Data tracing was turned on and a data transfer connection was established.

ACTION: Use this file for debugging purposes.

CAUSE: The FTP type command was entered without any parameters while in byte-stream mode.

ACTION: None.

CAUSE: Either the file name was so long that appending (.1) surpassed the maximum legal file name length, or every appendage from (.1 up to .99) was tried and no unique name could be found.

ACTION: Try a different, possibly shorter, file name.

CAUSE: Attempt to transfer a non-standard MPE file in append mode.

ACTION: Do not transfer non-standard MPE files in append mode.