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

492 Chapter21
Logging Location Codes
Control Process Logging Location Codes
ACTION: None. The network was not started. See Appendix A ,
“Submitting a CR,” of this manual.
266 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: NETCP tried to search the NMCONFIG file to determine if an
NI having a specific name was configured or not, but after successfully
opening the file it was unable to close it (PARM = 32-bit status returned
by the call to nmconfclose).
ACTION: This error in itself was not fatal, and NETCP continued.
However, the NMCONFIG file may be inaccessible. Check that the
NMCONFIG file exists and is not already opened by some other user,
such as someone running NMMGR. If this is not the problem and the
message persists, see “Appendix A , “Submitting a CR,” of this manual.
267 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: While creating an NI because a network was starting, NETCP
encountered an error trying to create a new mapping table for the NI
(PARM = 32-bit status returned by the call to map_create_table).
ACTION: The network was not started. Depending on the error, it is
possible too much frozen memory is being used by the system, but this
can change with time. Use GLANCEXL or a similar utility to check
memory usage by the system. If memory is not the cause and the
problem persists even if retried after a suitable waiting period, see
Appendix A , “Submitting a CR,” of this manual.
268 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: While creating an NI because a network was starting, NETCP
successfully created a new mapping table for the NI, but then
encountered an error trying to add the NETCP entity into the table
(PARM = 32-bit status returned by the call to map_add_entity).
ACTION: The network was not started. See Appendix A , “Submitting a
CR,” of this manual.
278 CLAS0002 MESSAGE: INTERNAL ERROR; Configuration file error
CAUSE: While processing a :NETCONTROL command to start or update a
network or add a link, NETCP successfully opened the NMCONFIG
file, but was unable to lock it (PARM = 32-bit status returned by the call
to nmconflockfile).
ACTION: The command did not execute, and NETCP closed the open
file. Check that the NMCONFIG file exists and is not already opened by
some other user, such as someone running NMMGR. If this is not the
problem and the message persists, see Appendix A , “Submitting a CR,”
of this manual.