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

IMS Target Considerations

IMS Target Considerations

  • To reduce the risk of locking segments, you can reduce the commit frequency from PowerCenter.
  • If an IMS target contains fields to which blanks or no data will be written, define those fields as optional fields in the data map. Otherwise, PowerExchange will issue errors during the bulk data movement.
  • You cannot write data to IMS SDEP segments or to a segment that is below an unkeyed segment.
  • If you want to write data to a segment that is mapped by an OCCURS clause, change the copybook to identify each field in the OCCURS clause as a separate field and then remove the OCCURS clause. PowerExchange cannot generate a separate row for each occurrence defined by an OCCURS clause.
  • When you import the IMS data map into PowerCenter, verify that any CCK field that you want to use as a key field is identified as a key field.
  • Informatica recommends that you use a separate netport job to write IMS data. This practice enables you to access a PSB with write intent and to modify the JCL, as needed, for updated IMS data, such as the IEFRDER log.

0 COMMENTS

We’d like to hear from you!