Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Connecting to AS/400 on iseries system from DB2 on Windows

561 views
Skip to first unread message

simo...@gmail.com

unread,
Sep 19, 2012, 11:02:14 AM9/19/12
to
Hello folks,

I'm a Windows DBA and have been asked to setup DB2 federation to query AS/400 data from DB2 on Windows. I have got federation feature turned on on DB2 Windows server and got the below catalog commands executed successfully:

DB2 CATALOG TCPIP NODE ASNODE REMOTE ASSERV SERVER 8479
DB2 CATALOG DB PROD AS ASDB AT NODE ASNODE AUTHENTICATION DCS
DB2 CATALOG DCS DB ASDB AS PROD

However, when trying to connect to the database or trying to create server definition in DB2 Control Center, the connection hungs forever. In the mean time, if I do NETSTAT -a, I could see the connection is established to as400 system with the correct port number.

I wonder if something needs to be enabled in AS/400 system for this to work, as I have no problem to use Client Access ODBC connection from MS Access.

Any help would be appreciated.

Thanks
Simon

Marc Rauzier

unread,
Sep 19, 2012, 12:51:30 PM9/19/12
to
écrivait dans
news:37589cfd-c02f-4c0b...@googlegroups.com ce qui
suit:

> Hello folks,

Hello

>
> I'm a Windows DBA and have been asked to setup DB2 federation to
> query AS/400 data from DB2 on Windows. I have got federation
> feature turned on on DB2 Windows server and got the below catalog
> commands executed successfully:
>
> DB2 CATALOG TCPIP NODE ASNODE REMOTE ASSERV SERVER 8479

You may want to try to use drda service on port 443. As far as I know
for connecting from a DB2 machine, drda should be used.
Make also sure that drda service is started on AS400 side (STRTCPSVR
*DDM) if you try to connect to port 443.

> DB2 CATALOG DB PROD AS ASDB AT NODE ASNODE AUTHENTICATION DCS
> DB2 CATALOG DCS DB ASDB AS PROD
>
> However, when trying to connect to the database or trying to
> create server definition in DB2 Control Center, the connection
> hungs forever. In the mean time, if I do NETSTAT -a, I could see
> the connection is established to as400 system with the correct
> port number.
>
> I wonder if something needs to be enabled in AS/400 system for
> this to work, as I have no problem to use Client Access ODBC
> connection from MS Access.

Client Access ODBC uses as-file service (on port 8479) as you noted.

>
> Any help would be appreciated.
>
> Thanks
> Simon
>



--
Cordialement
Marc Rauzier
(pour me répondre, ne pas utiliser le from mais le reply-to)

simo...@gmail.com

unread,
Sep 19, 2012, 5:04:14 PM9/19/12
to marc.r...@laposte.net
Thank you Marc. I'll give that a try. Btw, do you know if DB2 Connect is also required on both systems, or federation feature and drda should be enough to make connections?
Thanks

simo...@gmail.com

unread,
Sep 19, 2012, 6:54:07 PM9/19/12
to marc.r...@laposte.net
Hi there Marc again:

Thank you very much for the advice. I now got federation going on to as400 system and Nicknames are working great without the need to install DB2 Connect. Basically the DRDA service just needed to be turned on in as400 system and then I used the correct port number of the DRDA service in the catalog command, in my case it is 446

Have a great day!
Simon

Marc Rauzier

unread,
Sep 20, 2012, 1:35:03 PM9/20/12
to
�crivait dans
news:055985c2-900f-4567...@googlegroups.com ce qui
suit:
For sure, it is 446. I made a mistake with my 443 :-) I don't know what
happened with my fingers !

Happy to see it works fine for you.

>
> Have a great day!
> Simon
>



--
Cordialement
Marc Rauzier
(pour me r�pondre, ne pas utiliser le from mais le reply-to)
0 new messages