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

Appendix A 199
NMS Error Messages
NM Error Messages
MESSAGE: Expects a name from one to eight characters long.
(NMERR 162)
NMERR 162 CAUSE: Returned after entering LINKCONTROL command incorrectly.
ACTION: Check the spelling and try again.
MESSAGE: Expects alphanumeric name starting with alphabetic.
(NMERR 163)
NMERR 163 CAUSE: Returned after entering LINKCONTROL command incorrectly.
ACTION: Check the spelling and try again.
MESSAGE: Expects a semicolon after link name parameter.
(NMERR 164)
NMERR 164 CAUSE: Returned after entering LINKCONTROL command incorrectly.
ACTION: Check the spelling and try again.
MESSAGE: Expects TRACE keyword. (NMERR 165)
NMERR 165 CAUSE: Returned after entering LINKCONTROL command incorrectly.
ACTION: Specify keyword and try again.
MESSAGE: Expects an equals sign after keyword. (NMERR 166)
NMERR 166 CAUSE: Returned after entering LINKCONTROL command incorrectly.
ACTION: Correct and try again.
MESSAGE: Specified linkname is not an active datacomm device.
(NMERR 171)
NMERR 171 CAUSE: The specified linkname does not exist.
ACTION: Check the spelling of your entry and try again.
CAUSE: The device specified is not configured.
ACTION: Check the list of configured devices and try again.
MESSAGE: Specified pathname is not a datacomm device.
(NMERR 172)
NMERR 172 CAUSE: The specified pathname is not a valid datacomm device
address.
ACTION: Check the pathname in the configuration file and re-enter.
MESSAGE: Unexpected internal error accessing configuration data.
(NMERR 175)
NMERR 175 CAUSE: An unexpected error has occurred.
ACTION: See “Submitting an SR” at the beginning of this appendix.