PowerExchange, in conjunction with PowerCenter, can move bulk data from or to a DB2 for i5/OS source or target database.
You can use either the PowerExchange DB2 or SEQ database access method. These access methods generally correspond to the DB2 for i5/OS SQL or system file access methods for processing database tables and data. The DB2 access method processes the source or target as relational DB2 objects, whereas the SEQ method processes the source or target as libraries, files, and members. The SEQ method enables you to specify all or selected members for bulk data movement processing.
Depending on the access method that you select, you might not need to create a data map. You can use the following strategies to define the bulk data movement:
To use the DB2 access method, you can define the bulk data movement entirely from PowerCenter. A data map is not required. From the PowerCenter Designer, import the metadata that PowerExchange reads from the DB2 catalog as a “DB2” source type. Then create a mapping. In the PowerCenter Workflow Manager, create and run a workflow to perform the bulk data movement.
Alternatively, in the PowerExchange Navigator, you can create a data map that specifies the “DB2” access method. Then import that data map into the PowerCenter Designer as a nonrelational source or target definition. In a data map, you can define user-defined fields and build expressions to populate them.
To use the SEQ access method, you must create a data map from the PowerExchange Navigator that specifies the “SEQ” access method. In the PowerCenter Designer, import the data map as a nonrelational source or target and create a mapping. From the PowerCenter Workflow Manager, create and run a workflow to perform the bulk data movement. With the SEQ access method, you can process all or some of the members in the database file and use file list processing.
Because the DB2 database runs on an i5/OS system, it is remote from the system on which the PowerExchange Navigator and PowerCenter Integration Service runs. Therefore, you must run an additional PowerExchange Listener on the remote i5/OS system and verify that PowerExchange can communicate with it.