|
|
|
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.
| MESSAGE: Error in loading keywords from FTP catalog. |
| Level: (FTPERR 3)
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. |
| MESSAGE: Command must be less than or equal to 255 characters. |
| Level: (FTPERR 5)
CAUSE: The user entered an FTP command which exceeded
255 characters.
ACTION: Try entering the command using fewer characters. |
| MESSAGE: ?Invalid command |
| Level: (FTPERR 6)
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. |
| MESSAGE: Not connected. |
| Level: (FTPERR 8)
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. |
| MESSAGE: Cannot connect to host: ! |
| Level: (FTPERR 9)
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. |
| MESSAGE: Invalid Command Syntax. |
| Level: (FTPERR 10)
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. |
| MESSAGE: Invalid reply code from remote server. |
| Level: (FTPERR 11)
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. |
| MESSAGE: Transfer Request Failed. |
| Level: (FTPERR 13)
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. |
| MESSAGE: Target File Could Not Be Opened. |
| Level: (FTPERR 14)
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. |
| MESSAGE: Some records were truncated during transfer. |
| Level: (FTPWARN 15)
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. |
| MESSAGE: End of File encountered on target file during transfer.
Target file not saved. Increase file limit and try again. |
| Level: (FTPERR 16)
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. |
| MESSAGE: 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. |
| Level: (FTPERR 17)
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. |
| MESSAGE: We only support stream mode, sorry. |
| Level: (FTPWARN 18)
CAUSE: The FTP MODE command was entered.
ACTION: None. |
| MESSAGE: We only support file structure, sorry. |
| Level: (FTPWARN 19)
CAUSE: The FTP STRUCT command was entered.
ACTION: None. |
| MESSAGE: We only support non-print format, sorry. |
| Level: (FTPWARN 20)
CAUSE: The FTP FORM command was entered.
ACTION: None. |
| MESSAGE: Verbose mode off. |
| Level: (FTPINFO 21)
CAUSE: The FTP VERBOSE command was entered when verbose was
enabled.
ACTION: None. |
| MESSAGE: Verbose mode on. |
| Level: (FTPINFO 22)
CAUSE: The FTP VERBOSE command was entered when verbose was
disabled.
ACTION: None. |
| MESSAGE: Debugging off (debug=0). |
| Level: (FTPINFO 23)
CAUSE: The FTP DEBUG command was entered when debug was
enabled.
ACTION: None. |
| MESSAGE: Debugging off (debug=1). |
| Level: (FTPINFO 24)
CAUSE: The FTP DEBUG command was entered when debug was
disabled.
ACTION: None. |
| MESSAGE: Using ascii mode to transfer files. |
| Level: (FTPINFO 25)
CAUSE: The FTP TYPE command was entered without any
parameters while in ASCII mode.
ACTION: None. |
| MESSAGE: Using binary mode to transfer files. |
| Level: (FTPINFO 26)
CAUSE: The FTP TYPE command was entered without any
parameters while in binary mode.
ACTION: None. |
| MESSAGE: Already connected to !; use user or close first. |
| Level: (FTPWARN 27)
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. |
| MESSAGE: Unknown Error Detected. Subsystem = !,
Information = !. |
| Level: (FTPERR 28)
CAUSE: An unknown error was detected from some underlying
subsystem.
ACTION: Seek the assistance of your Hewlett-Packard
representative. |
| MESSAGE: We only support MPEXL Fixed and Variable record format,
sorry. |
| Level: (FTPERR 29)
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. |
| MESSAGE: We only support MPEXL Standard files, sorry. |
| Level: (FTPERR 30)
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. |
| MESSAGE: We don't allow MPEXL file equates, sorry. |
| Level: (FTPERR 31)
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. |
| MESSAGE: Remote server received timeout. Closing connection. |
| Level: (FTPERR 32)
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. |
| MESSAGE: ExitOnError mode on. |
| Level: (FTPINFO 33)
CAUSE: The EXITONERROR command was entered while the
exit-on-error feature was disabled.
ACTION: None. |
| MESSAGE: ExitOnError mode off. |
| Level: (FTPINFO 34)
CAUSE: The EXITONERROR command was entered while the
exit-on-error feature was enabled.
ACTION: None. |
| MESSAGE: Invalid IP address. |
| Level: (FTPERR 35)
CAUSE: An invalid IP address was used while trying to
open a connection.
ACTION: Refer to the body of this manual for assistance. |
| MESSAGE: Performing an ASCII transfer to a binary file. |
| Level: (FTPWARN 36)
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. |
| MESSAGE: Performing a binary transfer to a binary file. |
| Level: (FTPWARN 37)
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. |
| MESSAGE: Error opening data connection. |
| Level: (FTPERR 38)
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. |
| MESSAGE: ?Ambiguous command. |
| Level: (FTPERR 39)
CAUSE: A non-unique command string was entered at the
ftp> prompt.
ACTION: Check the command spelling and try again. |
| MESSAGE: Connected to !. |
| Level: (FTPINFO 40)
CAUSE: A connection request to a remote FTP server was accepted.
ACTION: None. |
| MESSAGE: Interactive mode on. |
| Level: (FTPINFO 41)
CAUSE: The PROMPT command was issued while prompting was
disabled.
ACTION: None. |
| MESSAGE: Interactive mode off. |
| Level: (FTPINFO 42)
CAUSE: The PROMPT command was issued while prompting was
enabled.
ACTION: None. |
| MESSAGE: Lower case on. |
| Level: (FTPINFO 43)
CAUSE: The CASE command was issued while "Forcing Lower
Case" was disabled.
ACTION: None. |
| MESSAGE: Lower case off. |
| Level: (FTPINFO 44)
CAUSE: The CASE command was issued while "Forcing Lower
Case" was enabled.
ACTION: None. |
| MESSAGE: File accessed exclusively. |
| Level: (FTPERR 45)
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. |
| MESSAGE: File name too long. |
| Level: (FTPERR 46)
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. |
| MESSAGE: Indirect file not found. |
| Level: (FTPERR 47)
CAUSE: The indirect file name specified in the mput command
was not found: "mput ^filename".
ACTION: Make sure the indirect file exists. |
| MESSAGE: Could not change directory to "!". |
| Level: (FTPERR 48)
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. |
| MESSAGE: Connection time-out value set to ! seconds. |
| Level: (FTPINFO 49)
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. |
| MESSAGE: Store unique mode on. |
| Level: (FTPINFO 50)
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. |
| MESSAGE: Store unique mode off. |
| Level: (FTPINFO 51)
CAUSE: The FTP sunique command was entered when
store-unique was enabled.
ACTION: None. |
| MESSAGE: Receive unique mode on. |
| Level: (FTPINFO 52)
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. |
| MESSAGE: Receive unique mode off. |
| Level: (FTPINFO 53)
CAUSE: The FTP runique command was entered when
receive-unique was enabled.
ACTION: None. |
| MESSAGE: Command tracing on. |
| Level: (FTPINFO 54)
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. |
| MESSAGE: Command tracing off. |
| Level: (FTPINFO 55)
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. |
| MESSAGE: Data tracing on. |
| Level: (FTPINFO 56)
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. |
| MESSAGE: Data tracing off. |
| Level: (FTPINFO 57)
CAUSE: The FTP trace command was entered when data tracing
was enabled.
ACTION: None. |
| MESSAGE: Command tracing file name is !. |
| Level: (FTPINFO 58)
CAUSE: Command tracing was turned on and a connection
to a remote system was established.
ACTION: Use this file for debugging purposes. |
| MESSAGE: Data tracing file name is !. |
| Level: (FTPINFO 59)
CAUSE: Data tracing was turned on and a data transfer
connection was established.
ACTION: Use this file for debugging purposes. |
| MESSAGE: Using byte-stream mode to transfer files. |
| Level: (FTPINFO 60)
CAUSE: The FTP type command was entered without any
parameters while in byte-stream mode.
ACTION: None. |
| MESSAGE: Unique file name cannot be created. |
| Level: (FTPINFO 61)
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. |
| MESSAGE: Append mode not valid with record or file type. |
| Level: (FTPERR 63)
CAUSE: Attempt to transfer a non-standard MPE file in
append mode.
ACTION: Do not transfer non-standard MPE files in append
mode. |
|
Complete PDF