After you install and configure InfoSphere Classic CDC for z/OS

Once you have installed and configured InfoSphere® Classic CDC for z/OS®, you can start using it.

Connecting a source data server to a target engine
Before you connect the source and target, ensure you have set up a source server and used Classic Data Architect to map tables.
Starting a data server
When you start a data server, you start those services that are configured to start in the configuration file for the server.
Stopping a data server
Stopping a data server ends the address space that the data server is running in after stopping all of the services that are running in that data server.
IMS-specific subscription processing
Before you create subscriptions, you must understand basic replication concepts such as log reading and validation. Then plan your subscription deployment by using design principles that optimize replication for your site
VSAM-specific subscription processing
Before you create subscriptions, you must understand basic replication concepts such as log reading and transaction processing.
Data type validation
Classic change data capture provides the option to enable additional validation of data types.
Using a column repair exit to manage badly formed data
You can write and implement a column repair exit to customize the repair value for a numeric SQL column that fails validation or cannot be converted to the SQL numeric data type.
System exits for change capture
System exits are programs that the data server calls at predefined processing points that allow you to reformat data, filter data, and control processing.
Using SMF for historical analysis
The monitor service can be configured to call an exit at periodic intervals to record processing metrics and subscription state changes for historical analysis.