-->hey again:
-----Original Message-----
From: Mike Lebermann [mailto:[EMAIL PROTECTED]]
--> java? i think i *did* see something about
that in the environment.
I had missed the piece about the AIX gateway. The NT
box has the SDK on in it and not DB2 Connect, that is
why the DCS directory is not on the NT machine.
-->yes. if i can't connect directly to the mainframe,
the at least i can try to do SQL via script on the
linux machine (just like the NT db2 interface).
Do you need to use the AIX gateway for the Linux
machine?
-->but i can't get any information out of the DB /
mainframe guys (not even documentation). what's funny
is that they referred me to another department that
*supposedly* have more information about the
mainframe configuration.
-->pass of the buck.
DB2 EE has Connect, so you would not need
the gateway.
--> it was explained to me last *night*, that
1) the company doesn't have a UDB environment
(so i'm guessing that DRDA doesn't exist)
2) i have to use valid SQL statements for DB2 version 6
(which is why
db2=> list tables for [user | system | all]
keeps failing. it's not supported {another guess} )
3) the AIX gateway is for passthrough only. there
isn't a database installation on the AIX server.
--> that to me seems untrue. how can you have
a passthrough setup with no application / program
that interfaces between the mainframe and a bunch
of clients (PC)? statement #3 what the DB2 department
told me word for word.
--> i don't have access to the AIX machine. i could try
to hack it, but i think i like my job (such as it is).
wish i could, though. that's why i thought that
i could compare the values of the DB2 for NT to
what i have on linux.
Can you get the catalog commands that
were issued on the AIX gateway to catalog the MVS
node, database, and DCS database? If you can, try
issuing those commands on the Linux box and then
attempt to connect to MVS. If that's not possible,
--> i'm very open to this option. i think it's *sort of*
working because i can authenticate my password (at
least it goes away and tries to come back), do something
like:
[snip]
db2=> connect to db2data user frank using password
SQL1334N The database server cannot be used to route a
remote request to a second database server in this
configuration.
[/snip]
--> and THAT'S the crux of the problem.
sorry it took so long to get to this point.
try an attach to the gateway from the Linux machine
and then issue your connect statement to MVS.
Mike
--- "Johnson, Shaunn" <[EMAIL PROTECTED]> wrote:
> 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.
[snip the rest]
-X
