HP 3000 Manuals HP 3000 Manuals
FTP User Messages and Errors
These error and warning messages may be returned to FTP users on MPE/iX
while using the FTP user program.
In the following list of messages and errors, the exclamation point (!)
represents a variable value.
(FTPERR 3) Error in loading keywords from FTP catalog.
Cause: The User-FTP program encountered an error while trying to load
the FTP command keywords onto it's 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.
(FTPERR 5) Command must be less than or equal to 255 characters.
Cause: The user entered an FTP command which exceeded 255 characters.
Action: Try entering the command using fewer characters.
(FTPERR 6) ?Invalid command.
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.
(FTPERR 8) Not connected.
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.
(FTPERR 9) Cannot connect to host: !
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.
(FTPERR 10) Invalid Command Syntax.
Cause: An FTP command was entered with invalid parameter syntax.
Action: Check the syntax of the desired command in the HP ARPA FTP
User's Guide.
(FTPERR 11) Invalid reply code from remote server.
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.
(FTPERR 13) Data Transfer Request Failed.
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.
(FTPERR 14) Target File Could not Be Opened.
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.
(FTPWARN 15) Some records were truncated during transfer.
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.
(FTPERR 16) End of File encountered on target file during transfer.
Target file not saved. Increase file limit and try again.
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.
(FTPERR 17) End of File encountered on target file during transfer.
Data not & appended to target file. Copy target file to new
file with a larger & limit and append to the new file.
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.
(FTPWARN 18) We only support stream mode, sorry.
Cause: The FTP MODE command was entered.
Action: None.
(FTPWARN 19) We only support file structure, sorry.
Cause: The FTP STRUCT command was entered.
Action: None.
(FTPWARN 20) We only support non-print format, sorry.
Cause: The FTP FORM command was entered.
Action: None.
(FTPINFO 21) Verbose mode off.
Cause: The FTP VERBOSE command was entered when verbose was enabled.
Action: None.
(FTPINFO 22) Verbose mode on.
Cause: The FTP VERBOSE command was entered when verbose was disabled.
Action: None.
(FTPINFO 23) Debugging off (debug=0).
Cause: The FTP DEBUG command was entered when debug was enabled.
Action: None.
(FTPINFO 24) Debugging on (debug=1).
Cause: The FTP DEBUG command was entered when debug was disabled.
Action: None.
(FTPINFO 25) Using ascii mode to transfer files.
Cause: The FTP TYPE command was entered without any parameters while in
ASCII mode.
Action: None.
(FTPINFO 26) Using binary mode to transfer files.
Cause: The FTP TYPE command was entered without any parameters while in
binary mode.
Action: None.
(FTPWARN 27) Already connected to !; use user or close first.
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.
(FTPERR 28) FTP Unknown Error Detected. Subsystem = !, Information =
!.
Cause: An unknown error was detected from some underlying subsystem.
Action: Seek the assistance of your Hewlett-Packard representative for
assistance.
(FTPERR 29) We only support MPEXL Fixed and Variable record format,
sorry.
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.
(FTPERR 30) We only support MPEXL Standard files, sorry.
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.
(FTPERR 31) We don't allow MPEXL file equates, sorry.
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.
(FTPERR 32) Remote server receive timeout. Closing connection.
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.
(FTPINFO 33) ExitOnError mode on.
Cause: The EXITONERROR command was entered while the exit-on-error
feature was disabled.
Action: None.
(FTPINFO 34) ExitOnError mode off.
Cause: The EXITONERROR command was entered while the exit-on-error
feature was enabled.
Action: None.
(FTPERR 35) Invalid IP address.
Cause: An invalid IP address was used while trying to open a connection.
Action: Refer to the body of this manual for assistance.
(FTPWARN 36) Performing an ASCII transfer to a binary file.
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.
(FTPWARN 37) Performing a binary transfer to an ASCII file.
Cause: A Binary data transfer occurred to an MPE/iX ASCII 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.
(FTPERR 38) Error opening data connection.
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.
(FTPERR 39) ?Ambiguous command.
Cause: A non-unique command string was entered at the ftp> prompt.
Action: Check the command spelling and try again.
(FTPINFO 40) Connected to !.
Cause: A connection request to a remote FTP server was accepted.
Action: None.
(FTPINFO 41) Interactive mode on.
Cause: The PROMPT command was issued while prompting was disabled.
Action: None.
(FTPINFO 42 Interactive mode off.
Cause: the PROMPT command was issued while prompting was enabled.
Action: None.
(FTPINFO 43) Lower case on.
Cause: The CASE command was issued while "Forcing Lower Case" was
disabled.
Action: None.
(FTPINFO 44) Lower case off.
Cause: The CASE command was issued while "Forcing Lower Case" was
enabled.
Action: None.
(FTPERR 45) File accessed exclusively.
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.
(FTPERR 46) File name too long.
Cause: The filename specified is longer than the maximum allowed by MPE:
"FILENAME/LOCKWORD.GROUPNAM.ACCTNAME". As of release 4.5, MPE/iX
supports longer filenames, but unless the first character of that name is
a dot (.) or a slash (/), the name will be interpreted as an MPE name.
Action: Specify a file name that is shorter or starts with a dot or a
slash.
(FTPERR 47) Indirect file not found.
Cause: The indirect file name specified in the mput command was not
found: "mput ^filename".
Action: Make sure the indirect file exists.
(FTPERR 48) Could not change directory to "!".
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.
(FTPINFO 49) Connection time-out value set to ! seconds.
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.
(FTPINFO 50) Store unique mode on.
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.
(FTPINFO 51) Store unique mode off.
Cause: The FTP sunique command was entered when store-unique was
enabled.
Action: None.
(FTPINFO 52) Receive unique mode on.
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.
(FTPINFO 53) Receive unique mode off.
Cause: The FTP runique command was entered when receive-unique was
enabled.
Action: None.
(FTPINFO 54) Command tracing on.
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.
(FTPINFO 55) Command tracing off.
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.
(FTPINFO 56) Data tracing on.
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.
(FTPINFO 57) Data tracing off.
Cause: The FTP trace command was entered when data tracing was enabled.
Action: None.
(FTPINFO 58) Command tracing file name is !.
Cause: Command tracing was turned on and a connection to a remote system
was established.
Action: Use this file for debugging purposes.
(FTPINFO 59) Data tracing file name is !.
Cause: Data tracing was turned on and a data transfer connection was
established.
Action: Use this file for debugging purposes.
(FTPINFO 60) Using byte-stream mode to transfer files.
Cause: The FTP type command was entered without any parameters while in
byte- stream mode.
Action: None.
(FTPERR 61) Unique file name cannot be created.
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, possible shorter, file name.