Migrate DB2 tables to PostgreSQL or Oracle, over JDBC or through CoreIQ

DB2 tables are now a source for [[feature:dataiq-vsam-batch-data-migration|batch data migration]], next to VSAM datasets and IMS segments. A table is copied column to column into PostgreSQL or Oracle, from the same Import Legacy Schema flow: no new wizard.

Two ways to read DB2. Pick a DataIQ DB2 connection under Database connections and DataIQ reads it over JDBC. Or pick a CoreIQ connection's DB2 catalog and CoreIQ reads it for you, with its own access to the host, so DataIQ needs no DB2 credentials and no IBM driver. On a CoreIQ DB2 catalog, Browse asks which: Through CoreIQ or Over JDBC. Over JDBC uses the DataIQ connection that reaches the same database, or creates one with the host, port and database filled in, and you add the credentials.

Browse and map. Browse lists one schema of one database at a time, with Schema and Database pickers, and tables named SCHEMA.TABLE. The column view proposes each target type from the DB2 column type, with its length, precision and scale, and keeps the primary key. The database and schema you picked stay selected all the way to the mapping editor. A table that exists in more than one database asks which one to load from before it can be saved.

Load it like any other source. A run pages through each table in key order, so dry run, pause, continue, Fix it and rerun work as they do for VSAM. The run picker refuses a table imported twice, over JDBC and through CoreIQ or from two databases, and names both, so one run never loads the same table from two places.

AI clients can do it over MCP: list a CoreIQ connection's DB2 databases and tables, propose a table migration without changing anything, and apply it.

Tested against DB2 for z/OS. A table without a primary key can't be continued after a stop over JDBC; rerun it instead.