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

48 Chapter4
NFT/3000 Error Messages
MESSAGE: COMMAND LINE IS TOO LONG.
5 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.
MESSAGE: CALL TO GENMESSAGE FAILED.
6 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.
MESSAGE: KEYWORD DICTIONARY IS TOO LONG.
8 CAUSE: Probable internal error.
ACTION: See Appendix A, “Submitting an SR,” of this manual.
MESSAGE: COMMAND LINE CONTAINS TOO MANY PARAMETERS.
9 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.
MESSAGE: NO SOURCE FILE WAS SPECIFIED.
10 CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.
MESSAGE: NO CLOSING QUOTE WAS SPECIFIED.
11 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 (‘).
MESSAGE: ! IS AN INVALID DELIMITER BETWEEN SOURCE AND
TARGET.
12 CAUSE: Usually a typographical error.
ACTION: Retype and reissue the command.