QUESTION:
I have a customer that would like to put DB2/6000 on two RS/6000s and
make the data on either system available to the other. From my
reading of the announcement materials it doesn't appear that DB2/6000
supports this directly (DB2/6000 to DB2/6000) like DB2 for MVS does
since DB2/6000 is only offers DRDA-Application Requestor support.
1. Is this correct?
2. If I can't directly connect the two DB2/6000s via DRDA can I
put DB2 CS/6000 and DB2 CAE/6000 on each RS/6000 and address
both systems from a program? What would be the limitations on
on such an approach?
---------- ---------- ---------- --------- ---------- ----------
A: 1. You are correct. DB2 data cannot be "shared" between
two machines, and only DRDA requestor level is supported.
2. Both machines will need CS/6000 but the functionality
of CAE/6000 is included in the base DB2/6000 product.
So for the configuration you describe the two machines
will not need CAE/6000.
There will be a significant restriction on the use of
the two databases; the application code can be connected
to only one database at a time. Thus the application
must be coded to:
Connect to database1
Access database1
Commit any updates against database1
Connect to database2
Access database2
Commit database2.
It will not be possible to intermingle a fetch from database1
with an update/insert database2.
You may also explore the possibility of exporting data from
database1 to a flat file which is mounted by machine 2.
database2 could then load the data from the mounted datafile.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q648236 CNDLC
Additional search words:
CNDLC CONNECT CONNECTOR DB2 DEC93 IX OZNEW RISCDB2 RISCSYSTEM RS
SOFTWARE TOGETHER 6000 6000S
WWQA: ITEM: RTA000036574 ITEM: RTA000036574
Dated: 01/1995 Category: RISCDB2
This HTML file was generated 99/06/24~12:43:13
Comments or suggestions?
Contact us