Errors Generated if TCP/IP DDM Server on AS/400 Not Started (246706)

SYMPTOMS

If the TCP/IP DDM Server on the AS/400 is not started, the following data providers cannot connect over TCP/IP:

Microsoft OLE DB Provider for AS/400
VSAMMicrosoft OLE DB Provider for DB2Microsoft ODBC Driver for DB2

If the TCP/IP DDM Server on the AS/400 is not started, testing the connection for the data providers that are listed earlier will return the following error messages:

For Microsoft OLE DB Provider for AS/400 and VSAM:
Test connection failed because of an error in initializing provider. The partner LU does not recognize the TP name.
For Microsoft OLE DB Provider for DB2:
Test connection failed because of an error in initializing provider. Could not connect to specified host SQLSTATE: 08S01, SQLCODE: -603
For Microsoft ODBC Driver for DB2:
Connection failed [Microsoft][ODBC Driver for DB2][Microsoft DB2 OLE DB Provider]Could not connect to specified host SQLSTATE: 08S01, SQLCODE: -603

Following are other potential causes for TCP/IP related errors (SQLCODE: -603 and -602):

The IP address (or name) is incorrect.
The IP port is incorrect.

RESOLUTION

Verify status of TCP/IP DDM Server on the AS/400 by performing the following steps:

From an AS/400 command line, type the following command:
netstat

When the following menu appears, choose option number 3 (Work with TCP/IP connection status):

     1. Work with TCP/IP interface status 
     2. Display TCP/IP route information 	 
     3. Work with TCP/IP connection status

A list that is similar to the following will be displayed:

     Remote     Remote    Local
Opt  Address    Port      Port       Idle Time    State 
__   *          *         drda       001:13:15    Listen
__   *          *         ddm        001:13:15    Listen
__   *          *         ddm-ssl    001:13:15    Listen

The list should contain an entry with the Local Port listed as drda. Scroll through the list until this entry is located. If this entry is not present, the TCP/IP DDM Server has not been started.

To start the TCP/IP DDM Server, type the following command from an AS/400 command line:
strtcpsvr server(*ddm)
If successful, a message will appear on the screen that indicates that the DDM Server is starting.
Repeat steps 1 through 3 above to verify that the server has started properly.

It is also possible to automatically start the DDM server whenever TCP/IP is started on the AS/400 system. Issue the following command on an AS/400 command line to enable this functionality:

chgddmtcpa autostart(*yes)

MORE INFORMATION

For more information about using the commands that are mentioned eariler in this article, refer to the IBM OS/400 CL Reference V4R4 (Document Number SC41-5722-03).

Microsoft has updated Host Integration Server 2000 OLE DB Provider for DB2 and ODBC Driver for DB2 to provide specific SOCKET_ERROR messages. The messages are seen in DB2 Network Library internal tracing, specifically when Error Conditions is turned on.

To enable tracing, you use the Systems Network Architecture (SNA) Trace utility (Snatrace.exe). You might receive error messages when you connect, send, or receive over the Windows TCP socket. Following is an example format of a trace message: Windows TCPIP Socket Connection (10061): No connection could be made because the target machine actively refused it.
For additional information about the enhancement, click the following article number to view the article in the Microsoft Knowledge Base:

329818 Vague TCP/IP Socket Errors Are Returned for OLE DB2 Provider

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.