MasterCopy for DB2 on z/OS Modernization Guide

MasterCopy for DB2 on z/OS automates the creation of full image copies (FIC) and incremental image copies (IIC) of DB2 tablespaces. It uses generic names to select objects for backup and manages backup datasets, including automatic deletion of obsolete backups and log files.

MasterCopy uses JCL (Job Control Language) to define and execute backup jobs. Configuration files specify parameters such as tablespace names, dataset naming conventions, and retention policies.

MasterCopy manages backup datasets by automatically cataloging them and deleting obsolete copies based on user-defined retention policies. This helps to maintain storage efficiency and simplifies backup management.

MasterCopy integrates with DB2 catalog to identify tablespaces and their associated datasets. It also uses DB2 APIs to initiate and monitor backup operations.

The core operation involves defining a JCL job that invokes MasterCopy with specific parameters. For example, to take a full image copy of tablespace 'DSNDB04.TS001', you would specify this in the JCL along with dataset naming conventions and other options.

MasterCopy uses standard MVS dataset naming conventions. Parameters within the JCL control the high-level qualifier, low-level qualifier, and other attributes of the backup datasets.

MasterCopy does not expose REST or SOAP APIs. Integration is typically achieved through JCL scripting and scheduling tools.

MasterCopy relies on the z/OS operating system for communication and storage management. It uses standard z/OS facilities for dataset access and catalog management.

MasterCopy reduces the operational overhead associated with DB2 backup and recovery. By automating the backup process and managing backup datasets, it minimizes the risk of data loss and simplifies disaster recovery planning.

MasterCopy helps to meet compliance requirements by ensuring that DB2 data is regularly backed up and that backups are retained according to defined policies. This provides an audit trail for data protection and recovery.

By automating backup dataset management, MasterCopy reduces the need for manual intervention, freeing up DBAs to focus on other tasks. This improves overall operational efficiency and reduces costs.

MasterCopy leverages z/OS security features for authentication and authorization. It integrates with RACF (Resource Access Control Facility) or equivalent security systems to control access to backup datasets and the MasterCopy utility itself.

MasterCopy supports standard z/OS audit logging. All backup and recovery operations are logged, providing an audit trail for security and compliance purposes.

MasterCopy does not directly encrypt backup datasets. Encryption can be implemented using z/OS encryption facilities or third-party encryption products.

MasterCopy is administered through JCL and configuration files. Parameters within the JCL control the backup process, dataset naming, and retention policies. Configuration files define default values and other settings.

MasterCopy provides logging and reporting capabilities. Log files contain information about backup and recovery operations, including start and end times, dataset names, and any errors that occurred. These logs can be used for monitoring and troubleshooting.

MasterCopy requires access to DB2 catalog and tablespace datasets. Ensure that the user ID running the MasterCopy job has the necessary privileges to access these resources.