Merge/Modify for Db2 Modernization Guide

Merge/Modify for Db2 creates up-to-date image copies by merging existing image copies with Db2 logs. This reduces the time required to recover Db2 tables and databases.

The product uses JCL (Job Control Language) to define and execute the merge and modify processes. Configuration files specify the input image copies, Db2 logs, and output dataset characteristics.

Merge/Modify for Db2 supports merging full and incremental image copies with Db2 logs to create a consolidated, up-to-date image copy. It also allows for modifications to the data during the merge process, such as data masking or filtering.

The primary components include the merge utility, the modify utility, and the JCL execution environment. These components work together to read image copies and logs, apply changes, and create the updated image copy.

The core operation involves specifying the input image copies, Db2 logs, and output dataset using JCL. The merge utility then combines the data, applying any specified modifications. For example, a JCL job might specify an input full image copy, several incremental image copies, and a range of Db2 log records to be merged into a new image copy.

Merge/Modify for Db2 uses standard z/OS datasets for storing image copies and logs. It interacts directly with Db2 to access log data. No specific API is exposed for external integration.

The product relies on z/OS security for authentication and authorization. It does not implement its own user management system. Access to datasets and Db2 resources is controlled through z/OS security profiles.

Merge/Modify for Db2 generates standard z/OS SMF (System Management Facilities) records for auditing and logging. These records can be used to track merge and modify operations, as well as any errors or warnings encountered.

By merging image copies with Db2 logs, Merge/Modify for Db2 reduces the time required to recover Db2 tables and databases. This minimizes downtime and improves overall system availability.

The product helps to streamline the recovery process, reducing the need for manual intervention and minimizing the risk of errors. This can lead to cost savings and improved operational efficiency.

Merge/Modify for Db2 can be used to create consistent and up-to-date image copies for disaster recovery purposes. This ensures that critical data can be recovered quickly and reliably in the event of a disaster.

Merge/Modify for Db2 leverages z/OS security for authentication. It supports authentication methods such as RACF, ACF2, and Top Secret, depending on the z/OS security configuration.

The product uses the z/OS access control model, which is based on access control lists (ACLs). Access to datasets and Db2 resources is controlled through z/OS security profiles and permissions.

Merge/Modify for Db2 does not directly implement encryption. However, it can work with encrypted datasets and Db2 data, provided that the appropriate z/OS encryption facilities are configured.

The product provides audit logging through z/OS SMF records. These records capture information about merge and modify operations, including the user ID, datasets accessed, and any errors or warnings.

Merge/Modify for Db2 is administered through JCL and z/OS system commands. There is no dedicated GUI or web console. User management is handled entirely by z/OS security.

The main configuration parameters are specified in the JCL used to execute the merge and modify utilities. These parameters include the input image copy datasets, Db2 log datasets, and output dataset characteristics.

Monitoring is performed through z/OS system monitoring tools and by reviewing the SMF records generated by Merge/Modify for Db2. These records provide information about the status and performance of merge and modify operations.

The operations handbook should include procedures for creating and maintaining JCL jobs, monitoring merge and modify operations, and troubleshooting common errors. It should also cover security considerations and best practices.