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

188 AppendixC
Error Messages
NetIPC Errors
NetIPC Errors
This section includes NetIPC error messages (SOCKERRs) and the
form for submitting a service request (SR).
SOCKERRS
NetIPC are (32-bit) integers that are returned in the
result
parameter
of NetIPC intrinsics when the intrinsic execution fails. (A result of 0
indicates that the intrinsic succeeded.) In addition, both NetIPC errors
and Transport Protocol errors are returned in the IPCCHECK intrinsic:
NetIPC errors in the
ipcerr
parameter and Transport Protocol errors
in the
pmerr
parameter. Transport Protocol errors are documented in
the NS 3000/XL Error Message Reference Manual.
0 MESSAGE: SUCCESSFUL COMPLETION.
CAUSE: No error was detected.
ACTION: None.
1 MESSAGE: INSUFFICIENT STACK SPACE.
CAUSE: Area between S and Z registers is not sufficient for execution of
the intrinsic.
ACTION: :PREP your program file with a greater MAXDATA value.
3 MESSAGE: PARAMETER BOUNDS VIOLATION.
CAUSE: A specified parameter is out of bounds.
ACTION: Check all parameters to make certain they are between the
user's DL and S registers. If an array is specified, make certain all of it
is within bounds.
4 MESSAGE: TRANSPORT HAS NOT BEEN INITIALIZED.
CAUSE: A :NETCONTROL was not issued to bring up the network
transport.
ACTION: Notify your operator.
5 MESSAGE: INVALID SOCKET TYPE.
CAUSE: Specified socket type parameter is of an unknown value.
ACTION: Check and modify your socket type parameter.
6 MESSAGE: INVALID PROTOCOL.
CAUSE: Specified protocol parameter is of an unknown value.
ACTION: Check and modify protocol parameter.