NS3000/iX Error Messages Reference Manual (36923-90043)

48 Chapter4
NFT/3000 Error Messages
5 MESSAGE: COMMAND LINE IS TOO LONG.
CAUSE: Input command length exceeded the allowed maximum
(200 bytes).
ACTION: Ensure that the command input file is correct. If the command
is truly too long, global specifications may be used to shorten it.
6 MESSAGE: CALL TO GENMESSAGE FAILED.
CAUSE: DSCOPYMSG intrinsic could not retrieve the specified error string
from the NFT message catalog.
ACTION: Make sure that NFTCAT2.NET.SYS is present and not being
accessed exclusively by some other user. If so, then try running MAKECAT
to ensure that the file is in message catalog format. If the console
message says that the version number in the message catalog is not
current then obtain the proper version. Examine the NM log file to see
which file system error occurred when the FOPEN was attempted.
8 MESSAGE: KEYWORD DICTIONARY IS TOO LONG.
CAUSE: Probable internal error.
ACTION: See Appendix A , “Submitting a CR,” of this manual.
9 MESSAGE: COMMAND LINE CONTAINS TOO MANY PARAMETERS.
CAUSE: Too many delimiters were in the command line (each delimiter
corresponds to one parameter).
ACTION: If the command line was entered properly, try using global
specifications to reduce the number of parameters.
10 MESSAGE: NO SOURCE FILE WAS SPECIFIED.
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
11 MESSAGE: NO CLOSING QUOTE WAS SPECIFIED.
CAUSE: A matching apostrophe (’) or set of quotation marks (“ ”), was
not found.
ACTION: The punctuation surrounding the parameter is not of the same
type. They must both be either (‘ ’) or (“ ”).
12 MESSAGE: ! IS AN INVALID DELIMITER BETWEEN SOURCE AND
TARGET.
CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
13 MESSAGE: ! IS INVALID DELIMITER BETWEEN TARGET AND
KEYWORDS.
CAUSE: Usually a typographical error.