TCP/IP Error (SQL30081N)

[Wong Yew Loon]

Hi,

While configuring my DB2 Connect using the CCA to my AS/400 server. I
encounter this error trying to test the connection :

SQL30081N A communication error has been detected. 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 : "connect".
Protocol specific error code(s) : "10061","*","*". SQLSTATE=08001

It is apparently something to do with the TCP/IP services at the AS/400.
However, as a newcomer to the AS/400 & DB2 Connect, I would need experts
like you to advise me how to check and what commands to checks on
AS/400.

Thank you !!

Cheers,
Yew Loon

[Mitch Mitchell]

I had a similar problem connecting to 6.1 on AIX. It turned out that it
wasn't a TCP/IP error at all... EXTSHM=ON helped. Also, check that you
are NOT trying to perform multiple connections using a TYPE1
connection... it should be a TYPE 2.
--
Mitch
Director of Database Operations
iBooks.com
"Changing the world one book at a time"

Sent via Deja.com http://www.deja.com/
Before you buy.

[Wong Yew Loon]

Pls pardon me, what do u mean by TYPE 1 or TYPE 2 connection ? Is it set in
the DB2 Connect machine or on the AIX (in your case) or AS/400 server (for
my case) ?

[Darin McBride]

On Mon, 10 Jan 2000 18:02:43 +0800, Wong Yew Loon wrote:

>SQL30081N A communication error has been detected. 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 : "connect".
>Protocol specific error code(s) : "10061","*","*". SQLSTATE=08001
>
>It is apparently something to do with the TCP/IP services at the AS/400.
>However, as a newcomer to the AS/400 & DB2 Connect, I would need experts
>like you to advise me how to check and what commands to checks on
>AS/400.

Actually, usually this indicates a TCP/IP setup difficulty at the end it
shows up on - most likely on YOUR system. (The server gets this error when
issuing a db2start.)

Trying pumping up your diaglevel (you can do this via the CCA, too), and then
looking at the diag log to see what it's trying to do. It often is looking
for more TCP/IP resources than you currently have allocated - this may mean
tweaking with your TCP/IP setup somewhat.

[Blair Kenneth Adamache]

From the SQL Reference:

There are two types of CONNECT statements:

CONNECT (Type 1) supports the single database per unit of work (Remote
Unit of Work) semantics.

CONNECT (Type 2) supports the multiple database per unit of work
(Application-Directed Distributed Unit of Work) semantics.

The choice is made when the program is precompiled (you cannot do a CONNECT
TYPE 2 from the command line).

[David Marvin]

If I recall correctly, 10061 implies the service is not available at the
remote sight. I suggest
you PING your AS/400 to determine if it is alive. If not, then you must
ensureTCP/Ip is started on AS/400 and that you have started the DDM server
is started.

Wong Yew Loon wrote:

> Hi,
>
> While configuring my DB2 Connect using the CCA to my AS/400 server. I
> encounter this error trying to test the connection :
>

> SQL30081N A communication error has been detected. 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 : "connect".
> Protocol specific error code(s) : "10061","*","*". SQLSTATE=08001
>
> It is apparently something to do with the TCP/IP services at the AS/400.
> However, as a newcomer to the AS/400 & DB2 Connect, I would need experts
> like you to advise me how to check and what commands to checks on
> AS/400.
>