Message Reference

TCP/IP

For users of TCP/IP in a UNIX-based environment, the following table lists some of the error reason codes (errnos) that are most frequently encountered. It is not a complete list of errors. Errnos can be found in the file /usr/include/sys/errno.h. The errno number itself is indicated for each operating system.

Table 32. UNIX-based TCP/IP errnos.

Errno	Errno Number					Description
	AIX	HP-UX	Solaris	UnixWare	Linux
EINTR	4	4	4	4	4	Interrupted system call.
EAGAIN	11	11	11	11	11	Resource temporarily unavailable.
EBUSY	16	16	16	16	16	Resource busy.
EMFILE	24	24	24	24	24	The per-process file descriptor table is full.
EPIPE	32	32	32	32	32	Broken pipe.
EADDRINUSE	67	226	125	125	98	The specified address is already in use.
ENETDOWN	69	228	127	127	100	The network is down.
ENETUNREACH	70	229	128	128	101	No route to the network is available.
ENETRESET	71	230	129	129	102	The network has dropped the connection on reset.
ECONNRESET	73	232	131	131	104	Connection has been reset by the partner.
ENOBUFS	74	233	132	132	105	Insufficient buffer space resources were available in the system to complete the call.
ENOTCONN	76	235	134	134	107	The socket is not connected.
ETIMEDOUT	78	238	145	145	110	The connection timed out.
ECONNREFUSED	79	239	146	146	111	The connection has been refused. If you are trying to connect to the database, check that the database manager and TCP/IP protocol support at the server have been started successfully. If using SOCKS protocol support, also ensure that TCP/IP protocol support at the SOCKS server has been started successfully.
EHOSTDOWN	80	241	147	147	112	The host is down.
EHOSTUNREACH	81	242	148	148	113	No route to the host is available.

For more information on UNIX-based TCP/IP communication errors, refer to the technical reference manuals for the appropriate operating system.

For users of TCP/IP in an OS/2 environment, the following list shows errnos that are most frequently encountered. It is not a complete list of errors. Errnos can be found in the file nerrno.h This file is part of the TCP/IP product include files. It may not be present on your system if they have not been installed. The errno number itself is in parentheses.

• SOCEINTR (10003): Interrupted system call.

• SOCEMFILE (10024): Too many open files.

• SOCEPIPE (10032): Broken pipe.

• EADDRINUSE (10048): The specified address is already in use.

• ENETDOWN (10050): The network is down.

• ENETUNREACH (10051): No route to the network is available.

• ENETRESET (10052): The network has dropped the connection on reset.

• SOCECONNABORTED (10053): The software caused a connection abort.

• ECONNRESET (10054): Connection has been reset by the partner.

• ENOBUFS (10055): No buffer space available.

• ENOTCONN (10057): The socket is not connected.

• ETIMEDOUT (10060): The establishment of a connection timed out before a connection was made.

• ECONNREFUSED (10061): The connection has been refused. If you are trying to connect to the database, check that the database manager and TCP/IP protocol support at the server have been started successfully.

  If using SOCKS protocol support, also ensure that TCP/IP protocol support at the SOCKS server has been started successfully.

• EHOSTDOWN (10064): The host is down.

• EHOSTUNREACH (10065): No route to the host is available.

• SOCEOS2ERR (10100): OS/2 error.

For more information on OS/2 TCP/IP communication errors, refer to the OS/2 TCP/IP documentation.

For users of TCP/IP or IPX/SPX under Windows 95, Windows 98, or Windows NT, the following list shows error codes that are most frequently encountered. It is NOT a complete list of errors. Errors returned by WSAGetLastError() can be found in the file winsock.h.

• WSAEINVAL (10022): If this error is received on function WSASTARTUP, then the Windows Sockets version supported by the application is not supported by this DLL.

• WSAEMFILE (10024): There are no file descriptors available.

• WSAEWOULDBLOCK (10035): The socket is marked as non-blocking and the operation would block.

• WSAEINPROGRESS (10036): A blocking Windows Sockets operation is in progress.

• WSAENOPROTOOPT (10042): The option is unknown or unsupported.

• WSAEADDRINUSE (10048): The specified address is already in use.

• WSAENETDOWN (10050): The network subsystem has failed.

• WSAENETUNREACH (10051): The network can't be reached from this host at this time.

• WSAENETRESET (10052): The connection has been broken due to remote host resetting.

• WSAECONNABORTED (10053): The virtual circuit was aborted due to timeout or other failure. The network has dropped the connection on reset.

• WSAECONNRESET (10054): Connection has been reset by the partner.

• WSAENOBUFS (10055): No buffer space available, too many connections.

• WSAENOTCONN (10057): The socket is not connected.

• WSAETIMEDOUT (10060): The establishment of a connection timed out before a connection was made.

• WSAECONNREFUSED (10061): The connection has been refused. If you are trying to connect to the database, check that the database manager and TCP/IP protocol support at the server has been started successfully.

• WSAEHOSTUNREACH (10065): The network can't be reached from this host at this time.

• WSASYSNOTREADY (10091): The underlying network subsystem is not ready for network communication.

• WSAVERNOTSUPPORTED (10092): The version of Windows Sockets API support requested is not provided by this particular Windows Sockets implementation.

• WSAHOST_NOT_FOUND (11001): Host not found.

• WSATRY_AGAIN (11002): Host not found. Request to retrieve the hostname's IP address from the name server failed.

• WSANO_DATA (11004): Valid name, no data record of requested type. The name server or hosts file does not recognize the hostname, or the service name is not specified in the services file.

For more information on TCP/IP communication errors under Windows, refer to the Windows Sockets documentation.

[ DB2 List of Books | Search the DB2 Books ]