Level: 0 CLAS0000
CAUSE: Invalid port message.
ACTION: Examine "Info" section of log record. See
Appendix A "Submitting a CR"
of this manual.
MESSAGE: Internal error.
Level: 1 CLAS0000
CAUSE: Unable to create port in data segment table.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: Internal error.
Level: 2 CLAS0000
CAUSE: Unable to locate known entry in the name registry.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: Internal error.
Level: 3 CLAS0000
CAUSE: Received unsolicited PXP reply message.
ACTION: Examine "Info" section of log record. See
Appendix A "Submitting a CR"
of this manual.
MESSAGE: Internal error.
Level: 4 CLAS0000
CAUSE: Buffer Manager error.
ACTION: Examine "Info" section of log record. See
Appendix A "Submitting a CR"
of this manual.
Level: 6 CLAS0000
CAUSE: Socket registry process reported a socket error.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: Internal error.
Level: 7 CLAS0000
CAUSE: Socket registry was unable to build a socket path
report from the node's path report.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: Internal error.
Level: 11 CLAS0000
CAUSE: Unable to send or insert a port message.
ACTION: See Appendix A "Submitting a CR"
of this manual.
Level: 27 CLAS0000
CAUSE: Unable to create socket record.
ACTION: This is typically not an error condition. A total
of at least 8000 socket records can be opened simultaneously on
your system. If you do believe that there are not that many sockets
opened then submit an CR. Otherwise run your application when there
are fewer NETIPC applications active on your system.
Level: 35 CLAS0000
CAUSE: Failure in freezing the GSXDS. The GSXDS is a data
structure internal to the NETIPC Subsystem.
ACTION: Check the memory allocation on your system and see
Appendix A "Submitting a CR"
of this manual if a CR is needed.
MESSAGE: Internal error.
Level: 36 CLAS0000
CAUSE: Failure in creating new process.
ACTION: Check the files in NET.SYS to ensure that all
networking programs are installed. For example, make sure that
PT2PNSTN.NET.SYS exists. If files are ok, then see
Appendix A "Submitting a CR"
of this manual to submit a CR.
MESSAGE: None
Level: 0 CLAS0001
CAUSE: Socket name registry full.
ACTION: Call IPCNAMERASE to open slots in the socket
name registry.
MESSAGE: None
Level: 1 CLAS0001
CAUSE: Socket Give table full.
ACTION: Call IPCGET to open slots in the socket give
table.
MESSAGE: Port DST table full.
Level: 2 CLAS0001
CAUSE: The Port DST table is a data structure internal
to the NETIPC subsystem, not to be confused with MPE DST entries.
ACTION: Wait until fewer NetIPC applications are running
on your system. Try again.
Complete PDF