How to make homogeneous system copies sap

Pre-production environments improve operational reliability by decoupling test and development work from ongoing production. And it enables the development and test environments to be continuously supplied with consistent test data.

For a long time it was difficult to clone a complete production landscape consistently in a time-consuming and expensive manner.

BCV4 sets the standard in the area of ​​cloning complex application landscapes. It duplicates Db2 subsystems or Db2 data sharing groups, IMS subsystems or combined systems (DB2 / IMS / VSAM) in record time. The fully automatic, usually nightly, BCV4 cloning process renews preproduction using a scheduler-controlled job chain.

Pre-production environments updated consistently on a daily or weekly basis make quality assurance work easier. Copies (BCV5 / 6) or extracts (XDM) for test and development work can now be made from this at any time.

Benefits of BCV4

  • Operational safety for production
  • Secure, regular test data supply for testing and development
  • Cost reduction through automation
  • Light DBMS upgrade tests

 

BCV4 duplicates Db2 and IMS subsystems that run on the z / OS operating system. It sets the standard for creating Db2 subsystem clones. Creating, setting up and running preproduction environments, SAP homogeneous system copies, PeopleSoft test environments, QA system updates and general Db2 application testing becomes a simple job flow. BCV4 is the preferred solution for creating such environments. BCV4 is also an important tool for IT staff implementing Db2 version upgrades.

BCV4 supports “single” and “shared” environments and is compatible with copy services such as native ADRDSSU, Flashcopy, Snapshot, ShadowImage, etc. BCV4 also clones complex systems including combined IMS / Db2 environments. It automates the entire process: renaming the datasets, changing the VTOCs and VVDSse, creating new catalogs and recataloging all files. It also makes the necessary updates in Db2 Directory and Catalog and prepares Bootstrap Datasets and Active Logs. In other words, BCV4 makes the new Db2 subsystem clone immediately usable.

Major advantages
Easy to install and run: the user selects from a list of cloning configurations and navigates through a short sequence of intuitive definition steps. Only necessary information that cannot be found by BCV4 itself is requested from the user. For each clone project, BCV4 creates a job flow that goes from start to finish. The execution takes place either using the company's own scheduler or under manual control of the operating personnel or in BCV4's own automatic submit mode. This means that after the first job has run, all other jobs will be run automatically after their predecessors have successfully completed.

Every step that is necessary to clone a Db2 subsystem is contained in the job chain. The pitfalls of labor-intensive and error-prone tasks are eliminated. The time wasted on repetition is a thing of the past. Once set up, a clone definition can be reused as many times as desired. The following explanations save the need for tedious setup tasks and the coordination of Db2 / IMS experts. Cloning happens at the "push of a button".

How BCV4 clones
Cloning is about copying and renaming a lot of objects, and the faster it gets done the better. BCV4 uses installed hardware quick copy tools, standard ADRDSSU, or existing backups to make copies of volumes and datasets from the source Db2 or IMS subsystems. It runs specialized programs to rename and re-catalog all datasets on the target disks. It completes this task in a fraction of the time that is required by the standard programs.

After all data from the source has been copied and available, BCV4 runs specialized programs to make the name changes necessary for the Db2 catalog. It does not use SQL or a Db2 utility to make these changes. Here is the source of its speed. Time savings of 90% and more are often reported by our customers. As soon as the target DB2 subsystem is started at the end of this process, it has newly imported data and is ready for use. It is no magic, but solid craftsmanship with the utmost attention to detail that makes these performance improvements possible.

Summary
Cloning subsystems is no longer work for valuable Db2 experts who have to be entrusted with a time-consuming and tedious job that lasts for many hours or even days. Treat yourself to the luxury of an automated and scheduler-controlled process. BCV4 makes the creation of a clone "at the push of a button" a reality.

And best of all, it only takes minutes, not days, from start to finish

• Avoid labor-intensive and error-prone manual work.
• Reduce the time it takes to create Db2 clones from days to minutes.
• Clone Db2 subsystems in a 24 × 7 environment.
• Eliminate the need for system downtime.

Choose from seven predefined clone types and let the application guide you step by step with easy-to-use definition screens. This process leads to a correct clone definition. No more trying things out. All required parameters are made available ready for execution.

During the clone definition process, BCV4 enumerates all of the Db2 subsystems and retrieves all of the information necessary to complete the clone definition. There is no need to remember or look at the library names, BSDS names, active log names, ICF catalog names, aliases, volume names, etc. BCV4 finds all of this.

The BCV4 clone definition process finds all source information. BCV4 offers a simple means of renaming. It applies rules to the source values.