|
|
|
Table of Contents
- NetIPC Errors
- SOCKERRS
- Submitting an SR
This appendix includes the mapping of X.25 SOCKERRs to protocol module errors,
and the complete table of possible NetIPC errors (SOCKERRs).
In the IPCCHECK intrinsic, both socket errors (SOCKERRs) and the
corresponding protocol module errors (pmerrs) are returned.
The following SOCKERRs are mapped to pmerrs. Other SOCKERRs
can be returned to NetIPC with a corresponding pmerr of zero
(0).
| MESSAGE: PMERR = 5 Intrinsics : IPCCONNECT |
| Level: SOCKERR 46
CAUSE: UNABLE TO INTERPRET RECEIVED PATH REPORT — Unable
to find an X.25 address to call from the remote node name given.
ACTION: Check consistency between configuration file and
network directory. In order to map the node name to the X.25 address,
both the address key and the IP address are used. |
| MESSAGE: PMERR = 1 Intrinsic : IPCCREATE |
| Level: SOCKERR 55
CAUSE: EXCEEDED PROTOCOL MODULE'S SOCKET LIMIT. — All
call socket entries in the X.25 internal tables are in use.
ACTION: Remember to release call sockets when no
IPCCONNECT and IPCRECVCN are
expected. |
| MESSAGE: PMERR = 45 Intrinsic : IPCCONNECT |
| Level: SOCKERR 55
CAUSE: All connection entries in X.25 internal tables are in
use.
ACTION: Remember to shut the VC's that are no longer in
use. |
| MESSAGE: PMERR = 36 Intrinsic : IPCRECV, IPCSEND, IPCCONTROL |
| Level: SOCKERR 59
CAUSE: The inactivity timer has timed out.
ACTION: Shutdown the connection before re-opening
it. |
| MESSAGE: PMERR = 21 Intrinsic : IPCRECV, IPCSEND, IPCCONTROL |
| Level: SOCKERR 65
CAUSE: CONNECTION ABORTED BY LOCAL PROTOCOL MODULE. —
Greater than 30,000 bytes of data was received in a single message.
ACTION: Alter the remote application program to send smaller
messages. |
| MESSAGE: PMERR = 2 Intrinsic : IPCRECV, IPCSEND, IPCCONTROL |
| Level: SOCKERR 67
CAUSE: CONNECTION FAILURE DETECTED. — A clear packet has
been received. The remote system or network aborted the connection.
ACTION: Retrieve the cause/diagnostic field with
IPCCONTROL (to examine the cause), and issue
IPCSHUTDOWN on the virtual circuit. |
| MESSAGE: PMERR = 4 Intrinsic : IPCCREATE |
| Level: SOCKERR 106
CAUSE: ADDRESS CURRENTLY IN USE BY ANOTHER SOCKET. — The
requested protocol relative address is already used by another process
through another IPCCREATE call.
ACTION: Use another protocol relative address or wait for
previous process to release its call socket. |
| MESSAGE: PMERR = 7 Intrinsic : IPCCREATE, IPCRECV, IPCSEND, IPCCONTROL, IPCRECVCN |
| Level: SOCKERR 107
CAUSE: TRANSPORT IS GOING DOWN. — A NETCONTROL STOP
command has been issued. All connections have been aborted.
ACTION: Issue an IPCSHUTDOWN on all call sockets and
virtual circuit sockets. |
| MESSAGE: PMERR = 13 Intrinsic : IPCCONNECT |
| Level: SOCKERR 116
CAUSE: DESTINATION UNREACHABLE. — Outgoing access not
allowed. The destination X.25 address is either not configured in the
SVC path table or the security flags do not allow outbound calls to this
address. It could also be a problem with the network directory.
ACTION: Check the configuration of SVC path table security and
the network directory. |
| MESSAGE: PMERR = 17 Intrinsic : IPCRECV completing IPCCONNECT |
| Level: SOCKERR 117
CAUSE: ATTEMPT TO ESTABLISH CONNECTION FAILED. — A
connection could not be opened between the XL node and the DTC.
ACTION: Issue IPCSHUTDOWN on the virtual circuit,
check the DTC XNA card is working, and re-issue IPCCONNECT.
|
| MESSAGE: PMERR = 52 Intrinsic : IPCCONNECT |
| Level: SOCKERR 131
CAUSE: PROTOCOL MODULE DOES NOT HAVE SUFFICIENT RESOURCES
— The protocol module has run out of buffers.
ACTION: Try again later. Reduce network load by closing some
connections or increase the number of buffers in the
configuration. |
| MESSAGE: PMERR = 51 Intrinsic : IPCSHUTDOWN, IPCCONNECT |
| Level: SOCKERR 142
CAUSE: INVALID CALL USER DATA OPT RECORD ENTRY — Too much
call user data has been sent. The amount is determined by the "no
address flag" and use of the fast select facility. The maximum call user
data that can be sent is 128 bytes (with fast select).
ACTION: Send a smaller CUD, use fast select, or use the "no
address" option. |
| MESSAGE: PMERR = 14 Intrinsic : IPCCONNECT |
| Level: SOCKERR 143
CAUSE: INVALID FACILITIES SET OPT RECORD ENTRY — The
facility set passed as a parameter has not been found in the internal
facility set table.
ACTION: Use one of the facility sets defined in the
configuration or add a new one. |
| MESSAGE: PMERR = 10 Intrinsic : IPCRECV |
| Level: SOCKERR 146
CAUSE: RESET EVENT OCCURRED ON X.25 CONNECTION. — An
unsolicited reset packet was received.
ACTION: Use IPCCONTROL (request 12) to examine the
cause/diagnostic field. The connection is still up and operational but
some data may have been lost. |
| MESSAGE: PMERR = 3 Intrinsic : IPCCREATE |
| Level: SOCKERR 153
CAUSE: SOCKET IS ALREADY IN USE. — A single socket per
network interface can be created with the catch-all capability.
ACTION: Wait for catch-all socket to be released. |
| MESSAGE: PMERR = 12 Intrinsic : IPCRECV |
| Level: SOCKERR 156
CAUSE: INTERRUPT EVENT OCCURRED ON X.25 CONNECTION. — An
interrupt packet was received.
ACTION: Use IPCCONTROL (request 12) to get interrupt
data. The connection is still up and operational. |
| MESSAGE: PMERR = 18 Intrinsic : IPCRECV |
| Level: SOCKERR 158
CAUSE: CONNECTION REQUEST REJECTED BY REMOTE. — The
outgoing call was rejected either by the local DTC, the network, the
remote DTC or the remote host.
ACTION: Use IPCCONTROL (request 12) to retrieve the
cause/diagnostic field. Take action depending on cause/diagnostic using
table given. |
| MESSAGE: PMERR = 24 Intrinsic : IPCSEND, IPCCONTROL |
| Level: SOCKERR 160
CAUSE: INCOMPATIBLE WITH PROTOCOL STATE. — This
connection is currently in the reset state. Either a reset was sent and
the protocol is waiting for a reset confirmation, or a reset has been
received.
ACTION: If you issued the reset, then wait and reissue the call
later. Otherwise, issue IPCRECV to complete an incoming
reset. |
|
