Database Replication for IBM zOS is an S/390® Hitachi software product that controls the execution of ShadowImage functions within Hitachi enterprise storage systems. DataBase Divider requires a ShadowImage license key to be installed on the Hitachi storage system.
Features
- Database Replication can be used to create DB2 DSN1COPY JCL statements to copy one tablespace to another. A source tablespace is copied to a target tablespace by defining a DATABASE/TABLESPACE/CATALOG grouping of control cards to Database Replication.
- Any number of tables may reside in the source volumes, as long as the same number of tables are copied to the target volumes. Tablespaces may be simple, segmented, or partitioned. All page and segment sizes are supported. Multidataset non-partitioned tablespaces are supported, but the user is responsible for ensuring that the same number of datasets exist for both the target and source. The same is true for multiple partitioned tablespaces.
- Database Replication retrieves the information necessary for the DSN1COPY build process from the DB2 catalog at run time. Therefore both source and target database/tablespace must exist, or Database Replication will return a non-zero return code. S/390® catalog information is also examined at run time, and an indication of a current entry, along with a residence volume is noted.
Benefits
- Simplifies business operations and optimizes Database Administrator resources by providing customers with capability from an S/390 batch job to select, replicate, rename, and catalogue selected DB2 databases using ShadowImage. Database Replication also simplifies business operations by automating advanced functionality centered around the specific needs and requirements of DB2 customers.
- Protects information by enabling the replication of DB2 DataBase volumes within the same Logical Partition (LPAR) or another Logical Partition (LPAR).
- Protects the integrity of replicated data when used in conjunction with DataSet Replication for IBM zOS by providing an alternate method to produce an identical copy of DB2® Tablespaces. This ensures recovered data is in tact and protects access to mission critical information by facilitating workload sharing on the secondary volume.
