hi mike:
-----Original Message-----
From: Mike Lebermann [mailto:[EMAIL PROTECTED]]
Shaunn,
Something doesn't look right here. A couple of things
I noticed :
1. NT is running v5.2, don't know if that means
anything.
--> Correct. The DB2 for windows NT version is 5.2
as I understand it, the version should be one step
above or below the version of the DB2 server.
2. The db directory output (DB2DSNB) for NT is not for
the database you're connecting to (DB2DSNE). It looks
like an entry for an NT or Unix based database.
--> The db directory output for NT is just another
example. I should have specified the same database
when I created the output file. It doesn't matter
which database I try to connect to on the Linux side;
neither works (or, the process I'm taking is incorrect).
--> The gateway, itself, as I understand it is an AIX 4.3
machine. The database resides on OS/390 / MVS.
3. You do not have the DCS directory output displayed
for the NT machine.
--> This is the message I get when I do a 'list dcs directory'
on the NT connection:
db2 => list dcs directory
SQL1311N The Database Connection Services directory cannot be found.
--> I'm sorry. I did cut out the rest of the databases on the
NT side. I didn't think anyone needed to see the rest of
the list. I just grabbed the one I was using at the time.
The 'list node directory' is complete on both sides in the
example.
Have you "cropped" the output for the "list node" and
"list db directory" because it doesn't look complete?
--> At anyrate, it seems odd that I can't connect to the
gateway via Linux DB2 Connect like the NT side. Initially,
I wanted to examine creating the Linux system as an additional
gateway ... now I'll be happy if I can make it a client.
--> Thanks for the response, Mike!
-X
--- "Johnson, Shaunn" <[EMAIL PROTECTED]> wrote:
> Hi all:
>
> We have a command-line connection set up for us on
> NT machines that
> connect to a mainframe database "through a gateway".
> What we would
> like to do is replicate this same connection so we
> can query the same
> tables from a Linux-based machine. We have
> installed DB2-EE 7.1 on a
> Mandrake 8.1 system to support this. Unfortunately,
> the
> administrators for the mainframe database are
> unavailable, so we have
> to gather all relevant connection information from
> the NT client. See
> below for what we have so far. Everything seems to
> go great right up
> to the point of making a connection, then it says it
> can't cannot be
> used to route a remote request to a second database
> server. What
> gives? It can't be this hard, can it?
>
> Thanks for any info.
>
> -X / p. w.
>
>
> ################### ON NT ##########################
>
> C:\>db2
> (c) Copyright IBM Corporation 1993, 1997
> Command Line Processor for DB2 SDK 5.2.0
>
> db2 => list node directory
>
> Node Directory
>
> Number of entries in the directory = 1
>
> Node 1 entry:
>
> Node name = GATEWAY
> Comment =
> Protocol = TCPIP
> Hostname = GATEWAY
> Service name = 50000
>
> db2 => list database directory
>
> System Database Directory
>
> Number of entries in the directory = 1
>
> Database 1 entry:
>
> Database alias = DB2DSNB
> Database name = DB2DSNB
> Node name = GATEWAY
> Database release level = 8.00
> Comment =
> Directory entry type = Remote
> Authentication = SERVER
> Catalog node number = -1
>
> db2 => connect to db2dsne user fred using tu786ky
>
> Database Connection Information
>
> Database server = DB2 OS/390 6.1.1
> SQL authorization ID = FRED
> Local database alias = DB2DSNE
>
> db2 => select * from sales.region;
>
> ..... (table rows not shown) .....
>
>
>
> ########################### ON Linux
> #############################
>
> db2 => list database directory
>
> System Database Directory
>
> Number of entries in the directory = 1
>
> Database 1 entry:
>
> Database alias = DB2DSNE
> Database name = DB2DSNE
> Node name = GATEWAY
> Database release level = 9.00
> Comment =
> Directory entry type = Remote
> Authentication = DCS
> Catalog node number = -1
>
> db2 => list node directory
>
> Node Directory
>
> Number of entries in the directory = 1
>
> Node 1 entry:
>
> Node name = GATEWAY
> Comment =
> Protocol = TCPIP
> Hostname = gateway
> Service name = 50000
>
> db2 => list dcs directory
>
> Database Connection Services (DCS) Directory
>
> Number of entries in the directory = 1
>
> DCS 1 entry:
>
> Local database name = DB2DSNE
> Target database name = DB2DSNE
> Application requestor name =
> DCS parameters =
> Comment =
> DCS directory release level = 0x0100
>
>
> db2 => connect to db2dsne user FRED using tu786ky
> SQL1334N The database server cannot be used to
> route a remote request
> to a second database server in this configuration.
>
