Previous Topic Next topic Print topic

N300: TCP Error errmsgfunction( ) = errorcode

The indicated TCP/IP error occurred. The list below shows possible error codes and their associated error messages.
Restriction: This topic applies to Windows environments only.

Eight-digit error codes, including the following, indicate problems with DB2 or VTAM.

ErrorCode Description
00000008 Cannot connect to application.

On the machine where XDB Link is installed, start the Gateway Profile Utility and verify that the Remote APPLID setting matches the APPLID of the remote application. (If you are using an earlier version of the Gateway Profile Utility, this setting might appear as Remote Host instead of Remote APPLID.)
00040005 Bad user id and/or password.

Verify that the user ID is correct and valid (i.e., not revoked). Verify that the password is correct and current (i.e., not expired).

Note:

If the Password Expiration Maintenance Utility (PEM) is installed on the host, you can run the PEM utility on your workstation to quickly determine why the user ID and/or password was rejected (e.g., password expired, user ID revoked, user ID invalid). If the problem stems from an expired password, you can use PEM to update that password. See the "PEM Utility" chapter in the XDB Link User's Guide for information about using PEM to diagnose and correct user ID and password problems.

Five-digit error codes starting with 110 indicate problems with XDB Link.

ErrorCode Description
11004 Cannot connect to host.

Check the following:

  1. Verify that the TCP/IP connection on the host system is up and running.
  2. On the machine where the XDB Link is installed:
    • Make sure the HOSTS file contains an entry that defines the host system's IP address, and verify that this IP address is correct. Also make sure the line containing this entry has a hard return at the end.

      OR

      If using DHCP, make sure the host system's IP address is registered with a DNS server.

    • Make sure the SERVICES file contains an entry that defines the port used by the Host Option on the host, and verify that the port number is correct. Also make sure the line containing this entry has a hard return at the end.
  3. Start the Gateway Profile Utility and verify that:
    • The Remote HOST setting matches the name assigned to the host's IP address in the HOSTS file or the DNS server.
    • The Port setting matches the name assigned to the Host Option in the SERVICES file.
11002 Cannot connect to host.

Check the following:

  1. Verify that the TCP/IP connection on the host system is up and running.
  2. On the machine where the XDB Link is installed:
    • Make sure the HOSTS file contains an entry that defines the host system's IP address, and verify that this IP address is correct. Also make sure the line containing this entry has a hard return at the end.

      OR

      If using DHCP, make sure the host system's IP address is registered with a DNS server.

    • Make sure the SERVICES file contains an entry that defines the port used by the Host Option on the host, and verify that the port number is correct. Also make sure the line containing this entry has a hard return at the end.
  3. Start the Gateway Profile Utility and verify that:
    • The Remote HOST setting matches the name assigned to the host's IP address in the HOSTS file or the DNS server.
    • The Port setting matches the name assigned to the Host Option in the SERVICES file.

The following error codes indicate problems with the client machine.

Note:

Two-digit error codes (e.g., 35) are displayed if you are running under a 16-bit operating system such as Windows 3.1. Five digit error codes (e.g., 10035) are displayed if you are running under a 32-bit operating system such as Windows 95, Windows NT, or OS/2.

Errors marked with an asterisk (*) are ones that can occur if your XDBNET.INI file does not specify a valid TCP/IP address for the server you are attempting to access. When these errors occur, open the XDBNET.INI file and verify that the following values are correct for your server:

  • Server name
  • IPAddress
  • TCPPort
16-bith ErrorCode 32-bit ErrorCode Description
35 10035 Operation would block.
36 10036 Operation now in progress.
37 10037 Operation already in progress.
38 10038 Socket operation on non-socket.
39 10039 Destination address required.
40 10040 Message too long.
41 10041 Protocol wrong type for socket.
42 10042 Protocol not available.
43 10043 Protocol not supported.
44 10044 Socket type not supported.
45 10045 Operation not supported on socket.
46 10046 Protocol family not supported.
47 10047 Address family not supported by protocol family.
48 10048 Address already in use.
49 10049 Can't assign requested address.
50 10050 Network is down.
51 10051 Network is unreachable.
52 10052 Network dropped connection on reset.
53 10053 Software caused connection abort.
54 10054 Connection reset by peer. *
55 10055 No buffer space available.
56 10056 Socket is already connected.
57 10057 Socket is not connected.
58 10058 Can't send after socket shutdown.
59 10059 Too many references can't splice.
60 10060 Connection timed out. *
61 10061 Connection refused. *
62 10062 Too many levels of symbolic links.
63 10063 File name too long.
64 10064 Host is down. *
65 10065 No route to host. *
66 10066 Directory not empty.
93 10093 Unknown Error. *
Parent topic: N300 - N399
Previous Topic Next topic Print topic