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

Appendix A 237
NMS Error Messages
NMGR Error and Warning Messages
MESSAGE: No network interface found, or unknown type.
(NMGRERR 231)
NMGRERR 231 CAUSE: You may have spelled the name incorrectly.
ACTION: Check the spelling and reenter.
CAUSE: The type may be unknown.
ACTION: Check the type of the network interface name by going to
NETXPORT.NI (do a direct branch). File an SR if the type is labeled as
UNKNOWN. (See “Submitting an SR” at the beginning of this
appendix). Delete the unknown type and retry.
MESSAGE: Unable to open source NCONF file for copy.
(NMGRERR 232)
NMGRERR 232 CAUSE: File does not exist or is the wrong version.
ACTION: If in guided configuration, then NMAUXI.PUB.SYS could not
be opened. If performing a copy subtree, check the source file to make
sure it exists and is the correct version.
MESSAGE: Unable to open destination NCONF file for copy.
(NMGRERR 233)
NMGRERR 233 CAUSE: File does not exist or is the wrong version.
ACTION: If in guided configuration, then NMCONFIG.PUB.SYS or the
user file does not exist, or is corrupt. You may check the version by
running NMMAINT.PUB.SYS. You may also run NMMGRVER to
determine if your file is corrupt.
If performing a copy subtree, check the destination file to make sure it
exists. Check the version and check to see if the file is corrupt (as
above).
MESSAGE: No PC return value is on the Gosub stack.
(NMGRERR 234)
NMGRERR 234 CAUSE: There is an internal G-code error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: Illegal PC value specified in statement. (NMGRERR 235)
NMGRERR 235 CAUSE: There is an internal G-code error.
ACTION: See “Submitting an SR” at the beginning of this appendix.
MESSAGE: The Gosub stack is full. (NMGRERR 236)
NMGRERR 236 CAUSE: There is an internal G-code error.
ACTION: See “Submitting an SR” at the beginning of this appendix.