tcVISION Offers New Replication Processing Features...

tcVISION Version 4 ushers in a new era in enterprise data replication, featuring a greatly-enhanced modeling and mapping GUI and bi-directional replication between mainframe data sources and DB2, Oracle, and Microsoft SQL Server running on Linux, UNIX, and Windows (³LUW²).

tcVISION¹s advanced GUI modeler allows for the creation of a relational target schema based on non-relational sources, as well as mapping that schema back to the source. Additionally, the modeler has built-in functionality to perform table lookups, rules to accept/reject source data, wizards to define regular expressions to modify data, and date/time conversion facilities.

The bi-directional replication feature provides additional flexibility by allowing users to move data back and forth between the mainframe and LUW.

For example, with tcVISION, replication can be performed between IDMS on z/OS and DB2 for Linux running on a mainframe IFL processor. As always, thanks to tcVISION¹s unique ³stage processing² architecture, most of the CPU workload can be placed on the LUW platform, thus minimizing mainframe CPU utilization.

The following illustrate some tcVISION replication processing examples:

n:n Replication

This example shows replication of two DL/I segments into a DB2 table. Simultaneously, replication also takes place to an Oracle table with an identical layout.

Processing Definition Wizard

In addition to the normal field type-based conversion of input data to output data, field contents can also be created or processed based upon defined functions (e.g., expressions and operations). Multiple Connections

Return to Top of Page

Processing definitions can accommodate a target field or column being derived from different sources.

Record Type Replication

For cases where input data includes a ³record type indicator² field/column, the data can be split to different output tables based on the content of the indicator. The structure of the input data may differ depending on the record type. In this example, the record identifier is field WACODE. The indicator field itself is not linked to an output field because it is not part of the replication.

The colored shading of the fields after GISTRUCTURE and KBSTRUCTURE indicate that the data record has been redefined from this point on or a new structure is used.

Reverse Replication Record Type Processing

Multiple independent input sources can be replicated into one output table. The origin of the data is indicated by field content in the output table.

Return to Top of Page

Replication of an ADABAS PEs/MUs

ADABAS recurring fields can be mapped into separate output tables. Reverse Replication of a Field Table.

Data from an ADABAS PE or MU or a field table can be distributed to multiple target tables. During reverse replication, tcVISION ensures that the correct occurrences are created.

Reverse Replication of a Field Table

Data from an ADABAS PE or MU or of a field table are distributed to multiple target tables. During a backward replication the correct occurrences must be created.

CDC for LUW RDBMSs

In addition to the previously-supported mainframe data sources, tcVISION’s change data capture functionality has been extended to also support data sources like DB2 LUW, Oracle, and Microsoft SQL Server.

IMS Batch CDC for z/OS

Also, a new collector type of 'IMS-Batch' allows capture of from z/OS IMS batch applications (this had previously been available only for VSE). The current list of supported data sources is as follows: