Well if you are connecting to DB2 on big iron FROM the Linux guest, this
means you have TCP/IP connectivity to z/os and DB2. There is a component
that you need to install and configure on the desktop. Has this been done?
I've had DB2 connect 8.1 running for a while now, and while we didn't have
port 5001 blocked, it is still possible that you might have something on
your network blocking that port. Pursue that, but also make sure that the
desktop knows how and where to find DB2 connect. The configuration
assistant is what I used, and defined access to all three of our production
DB2 instances that are being pointed to by DB2 connect.
|---------+------------------------------->
| | Marcy Cortes |
| | <[EMAIL PROTECTED]|
| | sfargo.com> |
| | Sent by: Linux on |
| | 390 Port |
| | <[EMAIL PROTECTED]|
| | .EDU> |
| | |
| | |
| | 10/07/2003 05:46 PM |
| | Please respond to |
| | Linux on 390 Port |
| | |
|---------+------------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: DB2 connect question
|
>------------------------------------------------------------------------------------------------------------------------------|
The DB2 guys here have installed DB2 connect here under SLES 8. They say
that it works fine from on the Linux guest. However, when they tried to
get
through it, they suspect port 5001 is blocked or something. Does this
sound
familiar to anyone?
Marcy Cortes
Wells Fargo Services Company
