DB2 LUW are all DB2 and understand DRDA - it should be possible to ADDRDBDIRE (relational database directory entry) and work with them directly. - so far as I know - have not had opportunity to do it.

In some documentation on this I saw mention of the IMPORT and EXPORT utilities of DB2 on LUW - this sounds like Query Management stuff, and QM is common to all the IBM DB2 versions.

So I believe it should not be necessary to go to CSV and Java and anything else to work with DB2 on another platform.

Cheers
Vern

On 11/4/2015 8:52 AM, Buck Calabro wrote:
On 11/3/2015 8:20 PM, Steve Landess wrote:
I don't have all the details yet, but I have an associate who needs to
migrate data from an AS/400 - iSeries - IBM i system to a DB2 LUW
database, most likely running on a Windows server.

I am not yet sure which version of either platform yet, but can anyone
provide what options are available which do NOT require the $$$$ DB2
Connect feature on the midrange side?
I did a subset of our tables for a proof of concept for some GIS work.
The GIS software ran ONLY against DB2 LUW. I forget the details, and it
was a while ago. The budget was zero dollars and 'use your spare time'.

My recollection was that I fired off the API that extracted the SQL DDL
and cut/pasted that DDL onto LUW scripts which created the tables.
Tweaked for LUW differences. Extracting the DDL might be do-able
entirely from SQL now, depending on the IBM i release level.

Then I used Scott's JDBC wrappers to write some RPG programs that read
the IBM i tables (using the cycle, ha!) and then doing an 'INSERT INTO'
on the remote LUW twin table. Inefficient, but it met my needs. It may
be easier to write a 'pull' from the LUW side; I'm an RPG programmer, so
everything looks like an RPG problem to be :-)



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].