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

General Configuration Considerations

General Configuration Considerations

  • To reduce the number of locking conflicts, verify that the IMS program communications block (PCB) for each source IMS database is defined with the keyword PROCOPT=GO
    x
    . This setting provides read-only access to the IMS database.
  • If you plan to use IMS ODBA or a netport BMP job to access an IMS database, verify that the program specification block (PSB) is defined in the IMS SYSGEN.
  • PowerExchange does not support PSBs that were generated with the LANG=PLI keyword.
  • If you use an IMS HDAM, DEDB, or PHDAM database as a data source or lookup, PowerExchange cannot fully optimize database access. PowerExchange assumes that data is stored in random order, even if you store the data in sequential order.
    PowerExchange determines an access path that ensures that all candidate records are selected. For HDAM, DEDB, and PHDAM databases, PowerExchange accesses records sequentially and disregards any non-matching records. In the SELECT statements that PowerExchange builds for accessing data, you should include a WHERE clause with KEY=
    value
    .

0 COMMENTS

We’d like to hear from you!