Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Multiple-Record Writes to IMS Unload Data Sets

Multiple-Record Writes to IMS Unload Data Sets

During bulk data movement sessions, PowerExchange can use a multiple-record data map to read data from an IMS unload data set on z/OS and write the multiple records in a single pass to an IMS unload data set target. This process is called a
multiple-record write
.
When PowerExchange performs a multiple-record write, it preserves source sequencing information. To enable multiple-record writes with sequencing, select the
Multi-Record Datamaps
and
Use Sequence Fields
options in the
Import from PowerExchange
dialog box when you create the source and target definitions.
To perform multiple-record writes with sequencing, PowerExchange uses group source processing to read source data in a single pass and uses group target processing to write data to the target in a single pass.
PowerExchange generates sequence fields to pass metadata about the source record relationships to the target. After you enable multiple-record writes with sequencing for a PowerCenter workflow, the workflow can read the multiple-record source, use the generated sequence fields to preserve the sequencing information, and write data to the target in the same record sequence as in the source.
To determine the relationships among IMS record types, PowerExchange uses the segment information that you imported into the multiple-record data map from the DBD. PowerExchange uses the segment information to generate primary and foreign keys and sequencing metadata in the source and target definitions.
When you run a PowerCenter session, PowerExchange uses the generated key values to reconstruct and write the data to the target in the correct sequence. PowerExchange maintains the data in a sequencing and queuing cache on the Integration Service node. When PowerExchange writes data to the target, it deletes the generated key fields and sends the data across the network in the correct sequence to the target file.

0 COMMENTS

We’d like to hear from you!