IPX/SPX Programming Manual

Socket Errors
HP NonStop IPX/SPX Programming Manual528022-001
B-3
EALREADY (4103)
EALREADY (4103)
Cause. An operation is already in progress. For accept_nw and connect_nw calls,
there is already an outstanding call on the socket. For the send_nw call, the send
buffer is already full (see the SO_SNDBUF option of the setsockopt, setsockopt_nw on
page 5-49 call for increasing the size of the send buffer).
Effect. The call failed.
Recovery. Wait for the operation to complete and retry the call.
EBADF (4009)
Cause. The filedes or socket parameter specified in the call contained an invalid file
descriptor.
Effect. The call failed.
Recovery. Correct the file descriptor specification in the call and retry the call.
EBADSYS (4196)
Cause. Either an application attempted to write directly to the NonStop IPXPROTO
process, or an internal error occurred in one of the socket routines.
Effect. The operation failed.
Recovery. Direct writes to the NonStop IPXPROTO process are not permitted; use the
socket calls. However, if the problem appears to be an internal socket error, contact
your service provider.
ECONNABORTED (4119)
Cause. A connection was aborted by the internal software on your host machine.
Effect. The connection was closed.
Recovery. Close the socket. Reestablish the connection using the socket, bind,
and connect calls. If the problem persists, contact your service provider.
EALREADY
EBADF
EBADSYS
ECONNABORTED