RC/Migrator for Db2 Modernization Guide

RC/Migrator automates the process of migrating Db2 objects and data between Db2 subsystems. It uses a command-driven interface and configuration files to define migration jobs.

RC/Migrator uses configuration files, often referred to as control cards, to define the migration process. These files specify the source and target Db2 subsystems, the objects to be migrated, and any data transformations required.

RC/Migrator supports various Db2 object types, including tables, indexes, views, stored procedures, and user-defined functions. It also handles data migration, including data type conversions and data filtering.

RC/Migrator integrates with RC/Merger, a component that helps resolve naming conflicts and merge object definitions during migration. This ensures consistency and avoids errors when migrating objects with the same name.

Common operations include generating migration jobs, executing migration jobs, comparing object definitions, and reporting on migration results. The product uses a command-line interface (CLI) for these operations.

The basic syntax involves specifying the command, followed by parameters that define the source and target Db2 subsystems, the objects to be migrated, and any data transformations. For example: MIGRATE TABLE(table_name) SOURCE(source_db2) TARGET(target_db2).

RC/Migrator uses configuration files, also known as control cards, to define migration jobs. These files specify the migration parameters and object lists. The primary interface is the command-line interface (CLI).

RC/Migrator does not expose a public API (REST, SOAP, or native). It primarily operates through batch jobs and command-line interfaces. Integration is typically achieved through scripting and scheduling tools.

RC/Migrator reduces the manual effort required to migrate Db2 objects and data, minimizing errors and accelerating the migration process. This leads to faster deployment cycles and reduced operational costs.

By automating the migration process, RC/Migrator ensures consistency and accuracy, reducing the risk of data corruption or inconsistencies between Db2 subsystems. This improves data quality and reliability.

RC/Migrator helps organizations migrate to newer Db2 versions or platforms more efficiently, enabling them to take advantage of the latest features and performance improvements. This supports modernization efforts and reduces technical debt.

RC/Migrator leverages Db2's built-in security features for authentication and authorization. It supports authentication methods such as RACF, ACF2, and Top Secret, depending on the Db2 subsystem configuration.

RC/Migrator uses the access control model defined within Db2, which typically involves granting privileges to users or groups to access and manipulate Db2 objects. This is often role-based access control (RBAC).

RC/Migrator does not directly handle encryption. Encryption is typically managed at the Db2 subsystem level using Db2's built-in encryption capabilities for data at rest and in transit.

RC/Migrator logs all migration activities, including the objects migrated, the user performing the migration, and any errors encountered. These logs can be used for auditing and troubleshooting purposes.

RC/Migrator is administered through a command-line interface (CLI). User management is handled through the Db2 subsystem's security administration tools, such as RACF, ACF2, or Top Secret.

Key configuration parameters include the source and target Db2 subsystem names, the objects to be migrated, and any data transformation rules. These parameters are specified in the configuration files (control cards).

RC/Migrator provides logging capabilities that track migration activities and errors. These logs can be monitored using standard z/OS monitoring tools or by reviewing the log files directly.

RC/Migrator requires network connectivity between the z/OS system where it is running and the Db2 subsystems involved in the migration. The specific ports used depend on the Db2 configuration.