RC/Compare for Db2 Modernization Guide

RC/Compare for Db2 compares Db2 objects across different Db2 subsystems. It identifies differences in object definitions and generates change scripts.

RC/Compare generates DDL (Data Definition Language) scripts to synchronize Db2 objects. These scripts can be used with RC/Migrator to apply the changes.

Commonly compared objects include tables, indexes, views, stored procedures, user-defined functions (UDFs), and other database objects.

The comparison process involves extracting the metadata of the objects from both Db2 subsystems and comparing them based on their definitions. Differences are then highlighted in the generated change script.

The core operation involves specifying the source and target Db2 subsystems, selecting the objects to compare, and then executing the comparison. The generated output is a DDL script.

RC/Compare uses configuration files to store connection information for Db2 subsystems and to define comparison options. These files are typically customized for each environment.

RC/Compare does not directly expose APIs. It primarily functions through its ISPF interface and batch jobs.

RC/Compare uses standard Db2 connectivity protocols for communication with Db2 subsystems. This typically involves TCP/IP.

RC/Compare reduces the manual effort required to identify and synchronize differences between Db2 environments. This minimizes errors and accelerates the deployment process.

By automating the comparison and synchronization process, RC/Compare helps ensure consistency across Db2 environments, which is crucial for maintaining data integrity.

The generated change scripts can be reviewed and customized before execution, providing control over the changes being applied to the target environment.

RC/Compare leverages the security features of the underlying Db2 subsystems. Authentication is handled by Db2.

Access control is managed through Db2's grant and revoke privileges. RC/Compare operates within the security context of the user executing the comparison.

RC/Compare itself does not perform encryption. However, it operates within the security framework of Db2, which may include encryption at rest and in transit.

RC/Compare generates logs that record the comparison process and any errors encountered. These logs can be used for auditing purposes.

RC/Compare is administered through its ISPF interface and batch jobs. Configuration parameters are set in configuration files.

User management is handled by Db2. RC/Compare uses the existing Db2 user accounts and privileges.

Monitoring is typically performed by reviewing the logs generated by RC/Compare and by monitoring the execution of batch jobs.

Key configuration parameters include connection information for Db2 subsystems, object selection criteria, and comparison options.