Using the Node Management Services (NMS) Utilities (MPE/iX 7.0, 7.5)

Appendix A 245
NMS Error Messages
NMGR Error and Warning Messages
ACTION: Check the type of the network interface name by going to
NETXPORT.NI (do a direct branch). File a CR (Change Request) if the
type is labeled as UNKNOWN. (See “Submitting a CR” at the beginning
of this appendix). Delete the unknown type and retry.
NMGRERR 232 MESSAGE: Unable to open source NCONF file for copy.
(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.
NMGRERR 233 MESSAGE: Unable to open destination NCONF file for copy.
(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).
NMGRERR 234 MESSAGE: No PC return value is on the Gosub stack.
(NMGRERR 234)
CAUSE: There is an internal G-code error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMGRERR 235 MESSAGE: Illegal PC value specified in statement. (NMGRERR 235)
CAUSE: There is an internal G-code error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMGRERR 236 MESSAGE: The Gosub stack is full. (NMGRERR 236)
CAUSE: There is an internal G-code error.
ACTION: See “Submitting a CR” at the beginning of this appendix.
NMGRERR 237 MESSAGE: The Network interface must be of type X.25.
(NMGRERR 237)
CAUSE: The operation is illegal if the NI is not an X.25 link.
ACTION: Check to make sure that the NI is an X.25 link.