After you install and configure VSAM Remote Source

After you install and configure VSAM Remote Source, you can start using it.

Refreshing your replication environment
Before replication begins, perform a refresh operation to load the contents of your target database and synchronize its contents with your data source.
Refresh reporting and monitoring
You can monitor refresh progress in Management Console, by using CHCCLP, or by issuing DISPLAY,REPL commands.
Helper threads for concurrent refresh
Helper threads increase throughput during replication and concurrent refresh operations.
Validation of the replication environment
InfoSphere® Classic CDC for z/OS® validates key components to ensure that your environment is ready to start replication.
Handling of invalid data
Invalid data refers to source data that does not agree with the logical table mapping that defines the source data as a relational table for refresh and replication purposes.
Understanding database transaction sequence and latency
Maintain low latency in your replication environment by optimizing the number of subscriptions that you deploy. In some cases, good subscription design involves a trade-off between low latency and applying transactions in strict order.
Starting the container
Follow the instructions outlined in this topic to start the Podman container for VSAM Remote Source.
Stopping the container
To stop the VSAM Remote Source container, follow these steps.
VSAM-specific subscription processing
Before you create subscriptions, you must understand basic replication concepts such as log reading and transaction processing.