Thanks for the reply:
-----Original Message-----
From: Philip Nelson [mailto:[EMAIL PROTECTED]]
Shawn,
--> I will look for the book today.
A couple of things -
1) You should probably be looking at "The DB2 Universal DRDA Certification Guide" by Brandl, Bullock, Cook, Harbus, Janacek and Le, rather than the standard DB2 UDB Certification guide. It has a complete
guide to setting up links to the mainframe.
--> Didn't know the Linux box could be both. I am
trying to configure the Linux box as a server and I'm
cataloging a new database to it. Since that doesn't seem to
be working, does the book you mention specify how to make
a server be both a gateway AND a client?
--> My goal is to have multiple databases on the Linux
server and a way to get to a database on the mainframe.
The mainframe wants user/password authentication, so,
that's why I tried to configure the DB2 like you've seen it
below. But if there is a better way to do this, please
show me the way.
2) Is your Linux box the client or the gateway or both ?
--> One of my earlier tests included this, but I still had
the same error. I did not, however, include the security
statement. I will try that today.
3) I'd suspect you'd want to catalog the database as "AUTHENTICATION DCS", so that security checking is done by RACF or equivalent. There are a number of invalid combinations of the "SECURITY" and
"AUTHENTICATION" tokens. For example SECURITY=PROGRAM and AUTHENTICATION=CLIENT are not allowed. We'd need to see your gateway configuration, unless the client and gateway are the same
box (I suspect not since you are cataloging the gateway on your client).
--> Not sure I follow. The gateway (mainframe) IS suppose to be
the client. Isn't that why I have to authenticate via the
client? Maybe I've mis-read the docs. Can you elaborate
on this thought?
Thought : if you've already cataloged the "gateway" and are now cataloging a "client", both on the same box, maybe this has something to
do with you problem.
Phil Nelson
DB2 IT Consulting Ltd.
--Thanks again!
-shaunn
>
>
>
> Hi all:
>
>
> I'm new to DB2 and I need some help.
>
> I'm using DB2 UDB v. 7.1 Enterprise Edition on Mandrake Linux 8, kernel
> 2.4.10-pre8. I'm trying to connect to OS/390 MVS running DB2 6.1. I
> FINALLY figured out a good portion of how to get connected to my mainframe
> DB2 from my Linux Server. But now I have some 'remote request' issue that
> is just too odd. I -think- I've connected to the database on the mainframe
> correctly by the following:
>
>
> [excerpt]
>
> db2=> CATALOG TCPIP NODE gateway REMOTE gateway SERVER db2c<instance>
> db2=> CATALOG DCS DATABASE DB2DATA AS DB2DATA
> db2=> CATALOG DATABASE DB2DATA as DB2DATA at NODE gateway AUTHENTICATION
> client
> db2=> UPDATE dbm cfg using AUTHENTICATION client
> db2=> terminate
>
>
> joeuser@linuxserver:> db2stop
> joeuser@linuxserver:> db2start ; db2
> 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 = db2c<instance>
>
> db2=> list database directory
> System Database Directory
>
>
> Number of entries in the directory = 1
>
> Database 1 entry:
>
>
> Database alias = DB2DATA
> Database name = DB2DATA
> Node name = GATEWAY
> Database release level = 9.00
> Comment =
> Directory entry type = Remote
> Authentication = CLIENT
> Catalog node number = -1
>
>
>
>
> db2 => connect to db2data user <user_name> using <password>
>
> SQL1334N The database server cannot be used to route a remote request to a
> second database server in this configuration.
>
>
> [/excerpt]
>
> * What exactly is the last line talking about?
> * If this NOT the correct configuration, what other configurations are
> there?
> *How can I find this out?
> *Any examples on the web (I couldn't find anything different than what the
> docs at IBM and my
> DB2 UDB v 7.1 book by Baklarz and Wong)?
>
>
> Any suggestions or comments would be appreciated.
>
> Thanks!
