This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
hvr-software.com | [email protected] | 135 Main Street, Suite 850, San Francisco, CA 94105
DB2 z/OS, a popular legacy mainframe database, is the successor of the mainframe database, OS/390 from IBM. Many organizations want to maximize the value of the data that is stored into those mainframe databases while leveraging the advantages of cloud computing. HVR enables organizations to replicate and integrate data from their DB2 z/OS on-premises environments to the cloud.
This datasheet details HVR’s support for IBM’s DB2 z/OS as a source for Change Data Capture (CDC) and as a target for data integration.
DB2 z/OS CompatibilityHVR supports DB2 z/OS v11.1 as both as a source and a target. Supported encodings include UTF-8 and UTF-16, ASCII, ISO-LATIN-1, and EBCDIC (Western European and American). All data types except
ROWID are supported.
CONNECT TO DB2 Z/OSTo connect to DB2 z/OS HVR uses DB2 Connect running on a Linux, Windows or AIX server close to the mainframe. When DB2 z/OS is the source for CDC, the most resource-intensive HVR processing is to parse the logs. HVR offloads this processing to the server running DB2 Connect to avoid putting an extra load on the mainframe.
CONTINUED. CONNECT TO DB2 Z/OSHVR was built for the cloud using a scalable approach to distribute processing. With a modular architecture, HVR allows flexible configurations that can leverage compute resources on-premises and in the cloud. HVR compresses and encrypts the data as it flows between on-premises and the cloud so that your data is safe and secure.
To further protect data, HVR uses a firewall proxy. An on-premises proxy server opens up the firewall for just a single server on-premises (e.g. in a DMZ to enable connections to get into the local data center.) Due to its modern framework, HVR has the ability to move multiple streams of data from one or more sources to flow to one or more targets. This is great for companies wanting to share on-premises data into multiple cloud environments.
One-Time Load – Refresh – Compare and RepairOne-time load, in HVR’s terms Refresh, as well as Compare and Repair, starts with a “select” from the DB2 z/OS database. Parallelism can be specified across tables, and data is pulled out through an IBM’s DB2 Connect feature running on a Linux, Windows or AIX-based server. The IBM DB2 Connect feature combined with optimized network utilization supports efficient and fast data retrieval.
CDC from DB2 z/OSTo capture from z/OS, HVR needs to be installed on a separate machine from which HVR will access DB2 on z/OS machine. That separate machine can be a Windows or Linux or AIX environment. HVR requires IBM’s DB2 Connect for connecting to DB2 on z/OS. HVR calls external stored procedures (installed separately) on the z/OS machine to capture information from the DB2 log files. These stored procedures will extract the information from DB2 log files using the IFI 306 interface.
Target DB2 z/OSHVR uses DB2 z/OS DB2 Connect, IBM’s native connectivity protocol to connect to the database for data transfers, including the initial data load.
We accelerate data movement so that you can revolutionize your business. HVR is designed to move large volumes of data FAST and efficiently in hybrid environments for real-time updates.