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

Chapter 5 75
NetIPC (SOCKERRS) Error Messages
field. The connection is still up and operational but some data may have
been lost.
151 MESSAGE: COULD NOT OBTAIN A SEMAPHORE.
CAUSE: The attempt to obtain a semaphore before sending a message to
the protocol module failed.
ACTION: See Appendix A , “Submitting a CR,” of this manual.
153 MESSAGE: SOCKET IS ALREADY IN USE.
CAUSE: A single socket per network interface can be created with the
catch-all capability.
ACTION: Wait for catch-all socket to be released.
155 MESSAGE: INVALID X.25 FLAGS OPT RECORD ENTRY.
CAUSE: Invalid flag bits set in protocol specific flags option, or invalid
length specified for option, or user did not have NA capability.
ACTION: Check bits set and length specified. Bit numbering is from left
to right (0–31).
156 MESSAGE: INTERRUPT EVENT OCCURRED ON X.25 CONNECTION.
CAUSE: An unsolicited interrupt packet was received.
ACTION: Use IPCCONTROL (request 12) to get interrupt data. The
connection is still up and operational.
157 MESSAGE: NO VIRTUAL CIRCUIT CONFIGURED.
CAUSE: No VC configured in the configuration file.
ACTION: Check the configuration file for X.25.
158 MESSAGE: CONNECTION REQUEST REJECTED BY REMOTE.
CAUSE: The remote node received the connection request and rejected
it.
ACTION: The call may be retried later. Otherwise, the reason for the
reject must be known.
159 MESSAGE: INVALID X.25 D BIT SETTING.
CAUSE: The D bit setting is not consistent in configuration file of local
and destination node.
ACTION: Check the configuration file for X.25.
160 MESSAGE: INCOMPATIBLE WITH PROTOCOL STATE.
CAUSE: The user requested an operation which is not supported by the
protocol module.
ACTION: Verify the sequence of intrinsic calls.