Migrate DB2 for i (AS/400) tables through CoreIQ
DB2 for i (AS/400) tables are now a source for [[feature:dataiq-vsam-batch-data-migration|batch data migration]], the same way DB2 for z/OS tables are. Pick a CoreIQ connection's DB400 catalog in Import Legacy Schema, and CoreIQ reads the AS/400 for you, so DataIQ needs no IBM i credentials and no IBM driver.
Through CoreIQ or over JDBC. When a DataIQ DB2 for i connection reaches the same machine, the catalog says so, and Browse offers both: Through CoreIQ or Over JDBC.
Browse and map. The AS/400's libraries are the schemas, and tables are named LIBRARY.TABLE. The column view proposes each target type with its length, precision, scale and nullability, read from QSYS2.SYSCOLUMNS, so nullable source columns stay nullable in the target table.
Load it like any other source. Dry run, pause, continue, Fix it and rerun work as they do for DB2 and VSAM. Timestamps load exact to the microsecond.
Host login off. A CoreIQ serving an AS/400 usually has host login off. DataIQ and the batch then store the CoreIQ connection's user and password for the host in a CoreIQ credentials session, as CoreIQ's own My credentials does, once CoreIQ refuses a call without one. An AS/400 host is offered only the catalogs it has an endpoint for, so it no longer lists Datasets or IMS-DB.
AI clients can do it over MCP: list a CoreIQ connection's DB2 for i tables, propose a table migration without changing anything, and apply it.
Tested through CoreIQ. A run reads every CoreIQ table from the host saved on its CoreIQ connection, so load each host's tables through a connection of its own. Over JDBC, DB2 for i columns are proposed NOT NULL: allow nulls in the column view before saving, or read through CoreIQ.