Hallo zusammen,

ich plage mich gerade mal wieder mit ODBC ab und hoffe, dass mir jemand von Euch helfen kann (nein, ich habe im Forum nichts passendes zu meinem Problem gefunden ;-).
Danke für Eure Mühe bereits im Voraus.

Mein Problem:
Auf einem WinXP-Arbeitsplatz ist IBM Personal Communications und IBM DB2 Client Configuration Assistant installiert. Auf diesem Client darf ich nicht CA installieren (wird vom Rechenzentrum nicht freigegeben).

Die Verbindung über den Assistenten ist wie folgt eingerichtet:

[NODE>GAL82000]
DB2SYSTEM=GAL820A
ServerType=DB2400
Protocol=TCPIP
Hostname=xxx.xxx.xxx.xxx
Portnumber=8471
Security=0

[INST>DB2]
instance_name=DB2
NodeType=2
ServerType=DB2NT

[DB>GAL82000:GAL820A]
Dir_entry_type=REMOTE
Authentication=NOTSPEC
DBName=GAL820A

[CLI_ODBC>GAL820A]
DataSourceName=GAL820A
DataSourceType=System
PWD=XXX
UID=***
PATCH2=6
PATCH1=1024
LOBMAXCOLUMNSIZE=1048575
LONGDATACOMPAT=1
ODBCParameters=Yes

Beim Testen der Verbindung erhalte ich den Fehler:

[IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "". Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=08001

Die Hilfe zu dem Fehler:

If you are trying to establish a new connection, possible causes
include the following:

o The remote database server has not been cataloged correctly
at the client.
o The database manager configuration file at the server has not
been configured with the proper communication parameters.
o The communication subsystem at the client node or server node
has not been configured correctly, or has not been started
successfully.
o The communication subsystem at the SOCKS server, if one is
being used, has not been configured correctly, or has not
been started successfully.
o The DB2COMM environment variable at the server doesn't
specify the communication protocol used by the client.
o The database manager at the server has not been started, or
has not been started successfully. One or more of the
communication protocols specified by DB2COMM may not have
been successfully started.

Refer to the token values for details. Depending on the protocol
being used and the communication function invoked, some tokens
may not be applicable. The following is the explanation of the
token values:
<... snip ...>
If the location information is not available at the time that the
error occurred, this token is not filled in.
<function> The name of the communication subsystem function that
returned the error code(s).
<rc1>, <rc2>, <rc3> The list of the available error codes and
subcodes that are specific to each protocol being used. Tokens
that are not applicable contain "*".
If the protocol being used is:
o TCP/IP
<... snip ...>
- If <rc3> is present and contains "0", it means that the
TCP/IP connection has been closed. This could be caused by one
of the following:
- The database agent at the server was forced off by the system
administrator.
- A database agent could not be started at the server because
the maxagents database manager configuration
parameter has been exceeded. Check the First Failure
Service Log (DB2DIAG.LOG) at the server to see if an
error message has been logged.
- The connection may have been closed by the remote server at
the TCP/IP level.
- The database agent at the server was terminated due to an
abnormal termination of a key database manager
process.
<... snip ...>
If you are trying to establish a new connection, check if:
1. The remote database server is cataloged properly on the
client node.
2. The database manager configuration file at the server is
configured with the proper communication related parameters.
If the database manager configuration parameters have been
updated at the server, ensure that you stop and then re-start
the database manager, for the changes to take effect.
3. The communication subsystems on both client and server nodes
are configured and started up properly.
4. The DB2COMM environment variable at the server specifies the
communication protocol used by the client.
5. The database manager at the server is successfully started.
Start database manager processing at the server should have
returned SQL1063, and not SQL5043. If SQL5043 is returned,
check the First Failure Service Log (DB2DIAG.LOG) for more
information.
6. A communication subsystem or network error has occurred.
If the problem persists, consult with your network administrator
and/or communication expert to determine the cause of the problem
using the set of tokens provided.

sqlcode: -30081
sqlstate: 08001