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

338 Chapter19
Logging Location Codes
Control Process Logging Location Codes
ACTION: Though no DCN message was sent, network startup probably
continued to completion, but connections over the affected network may
not work. Probably all the NETCP buffers have somehow been used up,
though it should have allowed for enough to support starting any
supported network configuration. Stop Transport and use NMMGR to
validate the NMCONFIG file and check for obvious file corruption, then
restart the network. If the problem persists, see Appendix A,
“Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR: Configuration file error
238 CLAS0002 CAUSE: During NETCP processing of a network start or update
command, after an earlier successful validation of the NMCONFIG file
a later validation of the file failed (PARM = 16-bit result code returned
by the call to validatenetxport).
ACTION: The specified network was not started. Possibly the
NMCONFIG file was being modified while networks were running, and
the changes made were incomplete or incorrect. Stop Transport and use
NMMGR to open and validate the NMCONFIG configuration file and
find any errors. Correct the errors and validate again. Then restart the
network.
MESSAGE: INTERNAL ERROR; Port
241 CLAS0002 CAUSE: During later phases of its initial startup, NETCP was unable to
create a process port for itself (PARM = 32-bit status returned by the
call to create_port).
ACTION: The transport was not started. There is a problem with the
operating system or a bug in NETCP; see Appendix A, “Submitting an
SR,” of this manual.
MESSAGE: INTERNAL ERROR; Configuration file error
242 CLAS0002 CAUSE: During later phases of its initial startup, after NETCP was
finished using the NMCONFIG file, it encountered an error while
trying to close the file (PARM = 32-bit status returned by the call to
nmconfclose).
ACTION: This error in itself was not fatal, and startup continued.
However, the NMCONFIG file may be inaccessible, and to be safe
NETCP assumed it still has the file open. If Transport is later stopped,
NETCP will again try to close the file. Possibly an earlier run of
NMMGR left the file in a bad state. If the problem occurs repeatedly,
see Appendix A, “Submitting an SR,” of this manual.
MESSAGE: INTERNAL ERROR; Internal resource error
251 CLAS0002 CAUSE: While creating and initializing a specific network NI because a
:NETCONTROL START command was issued, the NI module
configurator reported an error when trying to create the NI port data
area or port, or when sending an initialization message to the new NI
(PARM = 32-bit escape code returned by the call to