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

Single-Job Mode

Single-Job Mode

In single-job mode, PowerExchange maintains copies of previously read data maps in
job-level
memory. PowerExchange does not use ESCA memory to maintain information about data maps.
On subsequent reads of data maps, PowerExchange retrieves the data maps from
job-level
memory, which eliminates the overhead of enqueues, opens, points, reads, and closes of the data maps KSDS file.
When a data map changes or is deleted, PowerExchange deletes the copy of that data map in the cache. For changed data maps, PowerExchange does not add the data map to the cache again until the data map is actually used.
Single-job mode is more efficient than multiple-jobs mode because in single-job mode, the PowerExchange Listener job is the only job that updates the data maps file and the data maps cache does not become stale. Consequently, PowerExchange never needs to completely clear the cache like it does in multiple-jobs mode.
To configure PowerExchange to run data maps caching in single-job mode, define the following DBMOVER configuration statement:
DMXCACHE_MULTIPLEJOBS=N
For information about the DMXCACHE_MULTIPLEJOBS statement, see the
PowerExchange Reference Manual
.

0 COMMENTS

We’d like to hear from you!