Migrating away from ADABAS and Natural is not a simple task. Organizations have typically used these products to write mission-critical applications that are core to their business. Yet in today’s world, these applications are no longer mainstream, instead requiring special skills, hard to find skill sets, and proprietary environments.
Automated Migration Tool for ADABAS and Natural
Our fully 100% Automated Toolset that can efficiently convert your ADABAS / Natural applications to newer technologies. You can take your ADABAS off the mainframe or migrate it to a relational database DB2, Oracle or any RDBMS etc. You can migrate Natural applications to Java / J2EE. Our automated toolset has the specific capabilities for dealing with all the issues involved in converting ADABAS / Natural applications. Our tools provide not only the ability to migrate but also the ability to gain understanding of the application and enhance issues such as performance in the process.
Our experience and technology solutions greatly lowers the risk involved in migrating to DB2, Oracle, and SQL Server, and makes such a migration a smooth and easy process.
This is a comprehensive ADABAS solution that covers the entire ADABAS / COBOL environment – database remodeling, code and JCL migration, data-migration program generation, code “refresh”, and testing. The process migrates your ADABAS / COBOL applications to a relational system that provides the optimal balance between normalization and performance while being easy to maintain, and well documented.
The automated generation of data-migration programs by DBMSMigrator enables smooth data transfer from the ADABAS environment to the relational environment. This program generation process is based on source data models and the RDBMS data definitions and mapping rules that were created during data model mapping. This process also allows the migration programmer to add rules for data cleansing and modification that go beyond those defined by the mapping rules.
These programs extract the data from the ADABAS database into sequential files, and transform the ADABAS or VSAM format data to the destination relational table in accordance with the model mapping rules.
At the end of this process, load files are produced depending on the destination RDBMS. A standard load utility is used to read the files created during the transformation phase and load the data into the relational database.