Using the Node Management Services (NMS) Utilities (32022-90053)

Appendix A 249
NMS Error Messages
NMGR Error and Warning Messages
MESSAGE: Expected parameter after command. (NMGRERR 337)
NMGRERR 337 CAUSE: A parameter is needed after certain commands. This error
occurs if the user does not specify that parameter. OPENDIR: needs a
filename. MERGEDIR: needs a filename. EXPANDDIR: needs an
integer.
ACTION: Check syntax of the command or type “help” for more
information.
MESSAGE: Unknown or extra keyword parameter specified.
(NMGRERR 338)
NMGRERR 338 CAUSE: This occurs in DELETENODE or MERGEDIR when the
keyword local, global, keep, nokeep, or timestamp is spelled incorrectly
or you have a duplicate type of keyword. DELETENODE only allows
local or global keywords.
ACTION: Check spelling of keywords. Check for duplicate keyword
types. Type “help” for correct syntax.
MESSAGE: Illegal configuration file name. (NMGRERR 339)
NMGRERR 339 CAUSE: Configuration file name is invalid.
ACTION: Check the file name for validity. Also, make sure the name is
not too long.
MESSAGE: Illegal directory file name. (NMGRERR 340)
NMGRERR 340 CAUSE: Directory name may be too long, or contains illegal characters.
ACTION: Recheck file name specified.
MESSAGE: No keywords are allowed for this command.
(NMGRERR 341)
NMGRERR 341 CAUSE: This command does not allow keywords.
ACTION: Check syntax of the command or type “help” for more
information.
MESSAGE: Node Name length must be from 5 to 50 chars in length.
(NMGRERR 342)
NMGRERR 342 CAUSE: The node name length is wrong.
ACTION: Check the length of each segment in the node name. Each
segment (name,domain,org) must be 1–16 characters in length.
MESSAGE: Name segment in node name must be from 1 to 16 chars
in length. (NMGRERR 343)
NMGRERR 343 CAUSE: The name portion of the node name is the incorrect length.
ACTION: Fix the length of the name in NAME.domain.org.