BCV6 Modernization Guide
BCV6 is a data management product by UBS Hainer. Explore technical details, modernization strategies, and migration paths below.
Product Overview
BCV6 enhances DB2 environments by enabling consistent object copies while the objects remain online and available for updates.
It integrates with DB2's logging mechanism to ensure data consistency during the copy process.
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
What does BCV6 do?
BCV6 creates consistent copies of DB2 objects while they remain online and available for updates. It uses DB2 logs to roll forward any changes made during the copy process to the destination object, ensuring data consistency.
Is this a system, application, or tool?
BCV6 is a toolset designed to enhance data management capabilities within a DB2 environment. It provides specific functions for online object copying and data consistency.
What types of organizations use this?
Organizations that rely heavily on DB2 databases and require high availability, such as those in banking, finance, and insurance, commonly use BCV6. These organizations need to minimize downtime during data replication and backup processes.
When should we consider BCV6?
Consider BCV6 when you need to create consistent copies of DB2 objects without taking them offline. This is particularly useful for organizations with strict uptime requirements and large databases that are difficult to copy during maintenance windows.
What are the alternatives to BCV6?
Alternatives to BCV6 include other DB2 cloning tools and data replication solutions. Some examples are IBM Db2 Cloning Tool and various data replication products that support DB2. The key difference is BCV6's ability to maintain online availability during the copy process using DB2 logs.
Technical
What infrastructure is required?
BCV6 runs on the z/OS platform and is dependent on the DB2 subsystem. It requires access to DB2 logs to ensure data consistency during the copy process.
For mainframe products: Does this run in an LPAR?
BCV6 operates within a z/OS LPAR (Logical Partition) and leverages the DB2 subsystem for data access and manipulation. It integrates directly with DB2's logging mechanism.
Does this extend/enhance another product?
BCV6 enhances existing DB2 environments by providing online object copying capabilities. It extends the functionality of DB2 without replacing core DB2 functions.
What other products or components must be present for this to work?
BCV6 requires access to DB2's logs and control datasets. It also needs connectivity to the source and destination DB2 subsystems.
Business Value
How does BCV6 improve business operations?
BCV6 minimizes downtime during data replication, ensuring continuous availability of DB2 objects. This reduces the impact on business operations and improves overall service levels.
How does BCV6 reduce maintenance windows?
By enabling online object copying, BCV6 reduces the need for scheduled maintenance windows, allowing organizations to perform data replication and backups without interrupting critical applications.
How does BCV6 ensure data integrity?
BCV6 provides consistent DB2 object copies, ensuring data integrity and reducing the risk of data corruption during replication processes. This is crucial for maintaining accurate and reliable data across the enterprise.
Security
How does BCV6 handle security?
BCV6 leverages existing DB2 security mechanisms for authentication and authorization. It integrates with z/OS security systems, such as RACF, to control access to DB2 objects and functions.
What access control model is used?
BCV6 uses the access control lists (ACL) model inherited from DB2 and z/OS to manage user permissions and access rights. This ensures that only authorized users can perform specific operations on DB2 objects.
What audit/logging capabilities exist?
BCV6 integrates with z/OS audit and logging facilities to track all operations performed on DB2 objects. These logs can be used for security monitoring and compliance reporting.
Operations
How is BCV6 typically deployed?
BCV6 is typically deployed on-premise within a z/OS environment. It requires technical expertise in DB2 and z/OS to implement and maintain.
What ongoing operational requirements exist?
Ongoing operational requirements for BCV6 include monitoring the copy processes, managing DB2 logs, and ensuring the availability of the z/OS environment. Regular maintenance and updates are also necessary.
What are common implementation challenges?
Common implementation challenges include configuring DB2 logs correctly, ensuring network connectivity between source and destination DB2 subsystems, and managing the performance impact of online copy processes.
Ready to Start Your Migration?
Download our comprehensive migration guide for BCV6 or calculate your ROI.