Messages Reference
When using TCP/IP in a Unix environment, the following table
lists some of the errnos which the user may encounter
most frequently.
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 31. Unix TCP/IP errnos.
| Errno
| Errno Number
| Description
|
| AIX
| HP-UX
| Solaris
|
|---|
| EINTR
| 4
| 4
| 4
|
Interrupted system call.
|
| EAGAIN
| 11
| 11
| 11
|
Resource temporarily unavailable.
|
| EBUSY
| 16
| 16
| 16
|
Resource busy.
|
| EMFILE
| 24
| 24
| 24
|
The per-process file descriptor table is full.
|
| EPIPE
| 32
| 32
| 32
|
Broken pipe.
|
| EADDRINUSE
| 67
| 226
| 125
|
The specified address is already in use.
|
| ENETDOWN
| 69
| 228
| 127
|
The network is down.
|
| ENETUNREACH
| 70
| 229
| 128
|
No route to the network is available.
|
| ENETRESET
| 71
| 230
| 129
|
The network has dropped the connection on reset.
|
| ECONNRESET
| 73
| 232
| 131
|
Connection has been reset by the partner.
|
| ENOBUFS
| 74
| 233
| 132
|
Insufficient buffer space resources were available in the system to complete the call.
|
| ENOTCONN
| 76
| 235
| 134
|
The socket is not connected.
|
| ETIMEDOUT
| 78
| 238
| 145
|
The connection timed out.
|
| ECONNREFUSED
| 79
| 239
| 146
|
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
|
The host is down.
|
| EHOSTUNREACH
| 81
| 242
| 148
|
No route to the host is available.
|
For more information on Unix TCP/IP communication errors, refer to the technical reference
manuals for the appropriate operating system.
When using OS/2 TCP/IP, the following
is a list of errnos which the user may encounter
most frequently.
It is NOT a complete list of errors.
Errnos can be found in the file
nerrno.h.
The errno number itself is in parentheses.
For more information on OS/2 TCP/IP communication errors, refer to
the OS/2 TCP/IP documentation.
When using a DOS TCP/IP product (IBM TCP/IP for DOS,
FTP TCP/IP for DOS, Novell TCP/IP for DOS), the following
is a list of errnos which the user may encounter
most frequently.
It is NOT a complete list of errors.
The errno number itself is in parentheses.
- EPIPE (32):
Broken pipe.
- EADDRINUSE (48):
The specified address is already in use.
- ENETDOWN (50):
The network is down.
- ENETUNREACH (51):
No route to the network or host is available.
- ENETRESET (52):
The network has dropped the connection on reset.
- ECONNRESET (54):
Connection has been reset by the partner.
- ENOBUFS (55):
No buffer space available.
- ENOTCONN (57):
The socket is not connected.
- ETIMEDOUT (60):
The establishment of a connection timed out before a connection was
made.
- ECONNREFUSED (61):
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.
- EHOSTDOWN (64):
The host is down.
- EHOSTUNREACH (65):
No route to the host is available.
- ENOTINSTLD (66):
Protocol stack not installed.
For more information on DOS TCP/IP communication errors, refer
to the documentation for your DOS TCP/IP product.
When using TCP/IP or IPX/SPX under Windows 3.1, Windows 95, or Windows NT,
the following
is a list of error codes which the user may encounter
most frequently.
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.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
[ DB2 List of Books |
Search the DB2 Books ]