how to access db2 tables on aix from db2/390

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

zgh1970 - 16 May 2007 20:34 GMT

Hi, Friiends,
I am db2 UDB DBA on aix.

>From db2 UDB on aix, we can use federation by create server and then

nickname to access the tables on db2/390. For the security ,we can use
user mapping for for the federation serse.
All the setting federation server,nickname and user mapping controled
under the db2 udb database.

How can we do it from DB2/390 to access db2 UDB tables on aix?
Can we also create user mapping for the security?
All these set up in on the db2/390 database.

Thanks,
George
05/16

Reply to this Message

Dave Hughes - 16 May 2007 23:09 GMT

> Hi, Friiends,
> I am db2 UDB DBA on aix.
[quoted text clipped - 7 lines]
> Can we also create user mapping for the security?
> All these set up in on the db2/390 database.

Caveat: beyond running queries against DB2/390 I really don't know much
about it.

A quick glance at the InfoCenter for DB2 v8 and DB2 v9.1 on z/OS seem
to indicate that the usual federated data statements (CREATE WRAPPER,
SERVER, NICKNAME, etc.) aren't present - perhaps this feature is
present in DB2 for Linux/UNIX/Windows only?

That said, a search for "federated data" did turn up a few things with
vaguely familiar syntax under the reference section of "DB2 Data
Archive Expert"[1]. Perhaps this functionality *is* available under DB2
for z/OS, with some sort of bolt-on package?

[1] http://tinyurl.com/yrdtf7

Dave.

--

Reply to this Message

Lew - 17 May 2007 17:00 GMT

i believe db2/zos uses the ddf facility to access remote db2
databases. you add the definitions to the sysibm.location and
sysibm.ipnames tables. someone explained this to me once. i have
never done it myself.

Reply to this Message

Philip Nelson - 17 May 2007 22:54 GMT

> i believe db2/zos uses the ddf facility to access remote db2
> databases. you add the definitions to the sysibm.location and
> sysibm.ipnames tables. someone explained this to me once. i have
> never done it myself.

That's correct. Here are the specifics.

All the tables you need to update are in tablespace DSNDB06.SYSDDF.

For a typical connection you need to edit to following -

Table SYSIBM.IPNAMES
====================
LINKNAME = some-alias
SECURITY_OUT = P
USERNAMES = O
IBMREQD = N
IPADDR = ip-address-or-hostname

Table SYSIBM.SYSLOCATIONS
=========================
LOCATION = database-name-on-AIX
LINKNAME = as-specified-in-ipnames-above
IBMREQD = N
PORT = 50000 (or whatever port your AIX instance is listening on)
TPN = UDB

Table SYSIBM.USERNAMES
======================
TYPE = O
AUTHID = (spaces)
LINKNAME = as-specified-in-ipnames-above
NEWAUTHID = username-defined-on-AIX
PASSWORD = password-defined-on-AIX
IBMREQD = N

After setting up these rows, you need to bounce DDF to pick up the changes.

You'll notice that (for example) SPUFI has a LOCATION : and you can use
SPUFI and DSNTEP2 to run queries against UNIX DB2 databases if you bind the
packages remotely. You can't call stored procedures from SPUFI, but you
can write a simple REXX program to do that.

HTH

Phil

Reply to this Message