NetIPC 3000/XL Programmer's Reference Manual (5958-8600)
Table Of Contents
- 1 NetIPC Fundamentals
- 2 Cross-System NetIPC
- 3 NetIPC Intrinsics
- 4 NetIPC Examples
- A IPC Interpreter (IPCINT)
- B Cause and Diagnostic Codes
- C ErrorMessages
- D Migration From PTOP to NetIPC and RPM
- E C Program Language Considerations

186 AppendixC
Error Messages
SOCKERR 106 MESSAGE: PMERR = 4 Intrinsic : IPCCREATE
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.
SOCKERR 107: MESSAGE: PMERR = 7 Intrinsic : IPCCREATE, IPCRECV, IPCSEND,
IPCCONTROL, IPCRECVCN
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.
SOCKERR 116 MESSAGE: PMERR = 13 Intrinsic : IPCCONNECT
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.
SOCKERR 117 MESSAGE: PMERR = 17 Intrinsic : IPCRECV completing
IPCCONNECT
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.
SOCKERR 131 MESSAGE: PMERR = 52 Intrinsic : IPCCONNECT
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.
SOCKERR 142 MESSAGE: PMERR = 51 Intrinsic : IPCSHUTDOWN, IPCCONNECT
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.