Hi, I'm Bolo!
What would you like to know?
ASK BOLOPreview
Please to access Bolo.

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Commands
  3. Adabas Log-Based ECCR Commands
  4. Batch VSAM ECCR Commands
  5. CICS/VSAM ECCR Commands
  6. Datacom Table-Based ECCR Commands
  7. DB2 for z/OS ECCR Commands
  8. IDMS Log-Based ECCR Commands
  9. IMS Synchronous ECCR Commands
  10. IMS Log-Based ECCR Commands
  11. PowerExchange Agent Commands
  12. PowerExchange Condense Commands
  13. PowerExchange Listener Commands
  14. PowerExchange Logger for z/OS Commands
  15. PowerExchange Logger for Linux, UNIX, and Windows Commands
  16. pwxcmd Commands

Command Reference

Command Reference

Stopping the DB2 for z/OS ECCR

Stopping the DB2 for z/OS ECCR

Use the standard MVS STOP (P) command to stop the DB2 for z/OS ECCR immediately, even though in-flight UOWs might still exist. If records for incomplete UOWs are recorded in the PowerExchange Logger logs, PowerExchange cannot extract them until you restart the DB2 ECCR.
If you use the QUIESCE command instead of the MVS STOP command, restarting change data capture will be faster. The QUIESCE command waits until the ECCR reaches the DB2 quiesce point and no in-flight UOWs exist before stopping the ECCR. If the QUIESCE command fails to stop the ECCR for some reason, for example, because the ECCR is capturing changes for a long-running batch job, you can use the MVS STOP command.

Syntax

Use the following syntax:
{STOP|P}
task_name
The
task_name
variable is the DB2 for z/OS ECCR started task name or job name.

0 COMMENTS

We’d like to hear from you!