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

538 Chapter21
Logging Location Codes
NS Configurator Logging Location Codes
function code in the reply was not for a termination message
(PARM = 0).
ACTION: Resources allocated to the module were not released. Another
module may have unexpectedly sent a message to the reply subqueue of
NETCP’s Transport port, or the module which received the termination
message may be confused. If this problem occurs every time, see
Appendix A , “Submitting a CR,” of this manual.
22 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: When NETCP attempted to create a new protocol module for an
existing NI, after successfully creating a Compatibility Mode message
port DST for the module, an error occurred while trying to form a
Native Mode pointer into that DST (PARM = 32-bit status returned by
the call to convert_dst).
ACTION: The DST may not have been built correctly. There may be a
problem with the Ports subsystem of MPE, an addressing mismatch
between the protocol module code and its Module Configurator, or a bug
in the Module Configurator. See Appendix A , “Submitting a CR,” of this
manual.
24 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: When NETCP attempted to destroy a protocol module attached
to an NI, after a successful termination message exchange with the
module and successful release of all other resources, an error occurred
while trying to purge the modules message port (PARM = 32-bit status
returned by the call to purge_port).
ACTION: The module may have been unexpectedly reinvoked by
another processor, or there could be a problem with ownership of the
port or a bug in the Ports subsystem of MPE. If this problem occurs
every time, see Appendix A , “Submitting a CR,” of this manual.
25 CLAS0002 MESSAGE: INTERNAL ERROR; Internal resource error
CAUSE: When NETCP attempted to destroy a protocol module attached
to an NI, after a successful termination message exchange with the
module and successful release of all other resources, an error occurred
while trying to purge the modules Port Data Area (PARM = 32-bit
status returned by the call to release_object).
ACTION: The object may have already been released by MPE when the
port was purged, indicating a bug in the Module Deconfigurator.
Otherwise there may be a problem with the Virtual Space Management
subsystem of MPE. If this problem occurs every time, seAppendix A ,
“Submitting a CR,” of this manual.