Many of today’s mainframe applications that were developed in SAG Natural and Adabas are still mission critical and continue to deliver significant benefits to the organizations that use and rely upon them. Nevertheless, the Total Cost of Ownership and technological risk associated with these applications have now escalated to unacceptably high levels. CodeTurn for Natural to COBOL migration provides an opportunity to liberate these valuable and reliable business systems from their dependency upon non-strategic, legacy technologies and enable them to be integrated with state of the art components. For this purpose, CodeTurn supports COBOL, Java and C# as target languages. This Fact sheet specifically provides more insight into the COBOL target.
CodeTurn for Natural to COBOL migration takes any application developed in Natural (i.e. the programs, DDM’s, copycodes etc.) and automatically converts it into a fully identical application, but designed to run within an alternative environment on the same platform, or a different platform altogether. The new application is completely free of dependencies on Natural technology and, instead, uses modern and industry standard development tools such as Java, .NET and COBOL, to allow flexible application integration and extension.
The Anubex conversion process utilizes Natural’s SYSTRANS output format, in order to migrate the Natural artifacts. This approach largely isolates the Natural to COBOL conversion from the underlying system, therefore every Natural platform is supported, i.e. IBM Mainframe (z/OS, MVS), Fujitsu BS2000 and Unix.
A converted application can run on either Open Systems running Linux, Unix or Windows (LUW), or in the Cloud, or on IBM Mainframe (typically for COBOL only). The chosen target platform is simply selected as a configuration option during the conversion process.
When the target platform is LUW, additional Anubex tools handle the transformation of other source types, such as JCL, Assembler and COBOL programs etc., thus ensuring that the entire application runs on the new platform.
End-users can connect to the application with either a web‑browser, or their current Terminal Emulator.
The fact that the Terminal Emulator can optionally be retained for connection to the migration application enables the switch-over to be 100% transparent to end-users.
Many Natural mainframe applications are enhanced or integrated through 3rd party screen-scraping technology. Anubex' Natural to COBOL conversions provide byte-to-byte compatibility with the existing mainframe protocols; therefore screen-scrapers remain compatible, even on Open Systems.
The table below summarizes how all the Natural object types are converted into their COBOL counterparts.
After migration, all COBOL code is maintained using standard development tools on the chosen platform. The converted Predefined maps can be maintained using a WYSIWYG editor, to further facilitate application integration and modernization.
The below is the overview of the Architecture when migrating from Natural/Adabas to Linux, Unix, or Windows.
The below is the overview of the Architecture when migrating from Natural/Adabas to IBM Mainframe with COBOL/CICS/DB2.
Natural is recognized as a rich and powerful development environment. The Anubex Natural to COBOL migration tools provide support for advanced Natural language features, including:
The Adabas database and all its data are migrated automatically to a relational database (RDBMS).
Anubex has a 100% success rate, having completed numerous Natural to COBOL migration and modernization projects around the globe on both IBM mainframe and LUW target platforms. Each of these Natural to COBOL transformation projects has been delivered on time, within budget and to the complete satisfaction of the customer.
Get an instant copy of this Fact Sheet.