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

Creating a DB2 for z/OS Image Copy

Creating a DB2 for z/OS Image Copy

To create a full image copy as input for a bulk data movement session, define the JCL and control cards. Then submit the DB2 COPY utility job manually or from a job scheduler.
The JCL for creating a full image copy executes the DB2 DSNUTILB program. When the DB2 DSNUTILB program reads the control cards, it invokes the COPY utility to create the full image copy.
Include the following parameters in each COPY TABLESPACE statement:
  • FULL YES
  • SHRLEVEL REFERENCE
If you plan to use PowerExchange CDC to write changes to the target after materialization, include a QUIESCE TABLESPACE statement before the COPY TABLESPACE statements. The QUIESCE TABLESPACE statement causes PowerExchange to set event markers in the PowerExchange Logger log files. You need the event markers to create restart tokens for CDC. A restart token determines the start point in the change stream for a PowerExchange extraction.
For more information about creating restart tokens, see
PowerExchange Interfaces for PowerCenter
. For more information about creating image copies, see the appropriate IBM documentation.

0 COMMENTS

We’d like to hear from you!