Ending replication for IBM® Classic CDC for z/OS®

Classic CDC for z/OS supports three methods to end replication: Controlled, Immediate, and Scheduled End.

Controlled

In-progress work is completed before replication ends. If a refresh is in progress, the refresh for the current table is allowed to complete before replication ends. This option is the most appropriate for most business requirements and is the preferred method for ending replication in most situations.

Immediate

Stops all in-progress work and then ends replication. If a refresh is in progress, the refresh for the current table is interrupted and then replication ends. You should ensure that all dependent source database logs are available before ending replication by using this option. All the dependent source logs might need to be reprocessed when you restart the subscription. If a long-running transaction is being processed when you end replication with the Immediate option, replication might have to be resumed from the earliest open transaction in the database logs.

Scheduled End

This option is available when replication is started with the Continuous option. It processes all committed database changes in the source database and then ends replication at the indicated point. The following options are supported for Scheduled End:

Now

Stops replicating transactions at the current time.

Specific date and time

Stops replicating transactions at the local time for the specified Classic CDC server.

For more information about ending replication for Classic CDC, see STOP,REPL command.