CDC Guide for z/OS

10.5.5
- 10.5.8
- 10.5.6
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Starting Condense

On z/OS, you can run the Condense job as a batch job or a started task.

Generally, you use a started task to run a Condense task in continuous mode for a long time, and use a batch job to run a Condense job in batch mode as part of a scheduled batch job.

To start a Condense job as a batch job, submit the job to the MVS Job Scheduler by using products such as TSO/E, a job scheduler, or automation. PowerExchange provides sample JCL for running Condense as a batch job in the RUNLIB(CONDDB2) member.

To run the Condense job as a started task, place its PROC into the system PROCLIB. Then use the MVS START command to start the Condense started task. PowerExchange provides sample JCL for running Condense as a started task in the RUNLIB(PCNDDB2) member.

You cannot use the pwxcmd program to start a Condense job.

Before you start the Condense job, verify that the following conditions are met:

The PowerExchange Logger and Agent are started.

The checkpoint files are in the correct state for the start type:

For a cold start, verify that no checkpoint files exist with the CHKPT_BASENAME mask that is defined in the CAPTPARM member.

For a warm start, verify that all of the checkpoint files from the last Condense job exist and are available.

The capture registrations that are required for the Condense run are defined for the DBTYPE and DBID in the PowerExchange Navigator. If required, you can delete or deactivate registrations in the PowerExchange Navigator.

Starting and Stopping PowerExchange Condense

Cold Start Processing

Warm Start Processing

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal