TS Supplement (Includes RFC-1006 Support)

6 Socket Errors Returned by

TCP/IP to OSI/TS

107751 Tandem Computers Incorporated 6–1

This section lists the socket errors that can be returned in the external variable

errno

by the routines in the sockets interface library. This list is only a subset of the error

codes sent by TCP/IP. Only those errors that can be received by the OSI/TS process

are listed.

The descriptions given here are general; you should interpret each error according to

the type and circumstances of the call. For specific information on the meaning of an

error for a particular socket routine, see the description of the individual routine in the

Tandem TCP/IP Programming Manual.

These error codes can be displayed with the OSI/TS or OSI/AS SCF STATUS SU

command (the NSPFSErrorCode field), or by viewing PTrace records.

The socket errors are described in numerical order.

Note For internal errors, follow the standard procedures at your site for contacting the appropriate support

personnel. These procedures might involve contacting the local Tandem National Support Center or your

local Tandem Support representative. For information on contacting a Tandem representative, refer to

the Getting Help subsection in Section 8 of the Tandem OSI/AS Configuration and Management Manual.

4013 EACCES

Cause. A call to bind_nw specified an address or a port number that cannot be

assigned to a nonprivileged user. Only applications whose process access ID is in the

SUPER group (user ID 255,n) can bind a socket to a well-known port.

Effect. The bind_nw call failed.

Recovery. Rerun the TSP process with a process access ID in the SUPER group (user ID

255, n).

4022 EINVAL

Cause. An argument passed to one of the socket functions was invalid.

Effect. The call failed.

Recovery. This is an internal error.

4106 EMSGSIZE

Cause. The message was too large to be sent atomically, as required by the socket

options.

Effect. The call failed.

Recovery. This is an internal error.