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.
Anubex’s automated CodeTurn for Natural to C#, Natural to Java and Natural to COBOL modernization and migration solution 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.
Anubex' CodeTurn Adabas-Natural to C#, Adabas-Natural to Java and Adabas-Natural to COBOL migration solution takes any application developed in Natural (i.e. the programs, DDM’s, copycodes) 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 Natural to C#, Java and COBOL transformation process utilizes Natural’s SYSTRANS output format, in order to migrate the Natural artifacts. This approach largely isolates the Natural conversion from the underlying system, therefore every Natural platform is supported, i.e. IBM Mainframe (z/OS, MVS), Fujitsu Technology Solutions BS2000/OSD and Unix.
The converted Natural application can run on either IBM Mainframe or Open Systems running Linux, Unix or Windows (LUW), or in the Cloud. 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, their current Terminal Emulator, or a Java Swing/WPF client. 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 C#, Java and COBOL conversions provide byte-to-byte compatibility with the existing mainframe protocols; therefore screen-scrapers remain compatible, even on Open Systems.
The application’s character-based user interface is converted into a modern, open Java or .NET front-end that can be maintained using standard development tools like Eclipse and Visual Studio. Following the migration, developers can enhance the converted Natural Maps with graphical components such as drop-down fields, checkboxes and data lists.
For any migration project, and especially those that target a Mainframe platform, performance and CPU consumption are crucial acceptance criteria, because they directly impact the TCO of an application. Anubex ensure that two significant objectives are achieved in converting Adabas-Natural applications:
The converted application is tested with Anubex’s TestMatch, which reduces the time and effort needed to complete the project:
Learn more about the capabilities of TestMatch
Our experienced migration specialists, powerful tools and proved methodology can transform complex modernization projects in business-as-usual operations.
Join tens of companies and state agencies that have already used our methodology and tools in 100% successful projects.
Different options are available for migration of the Natural artifacts. To give an overview of what is currently possible, we define two categories: Object-Oriented solution or COBOL solution.
In today’s market, Object-Oriented code typically equates to either Java or .NET code that runs on LUW platforms.
Because the practice of code reuse through copycodes is no longer supported in modern languages such as Java and C#, the mapping of it may require inline code in the OO target.
After migration, all code is maintained using standard, industry leading development tools such as Visual Studio (for .NET code) or Eclipse (for Java code).
COBOL target code runs on either IBM Mainframe or Open Systems. The table below summarizes how all Adabas-Natural object types are converted into a COBOL counterpart.
After migration, all COBOL code is maintained using standard development tools on the chosen platform.
In conjunction with Anubex’ Waxwing technology, the converted *Predefined maps can be maintained using a WYSIWYG editor such as Eclipse or Visual Studio, to further facilitate application integration and modernization.
Anubex has a 100% success rate, having completed numerous Adabas-Natural to C#, Java and COBOL migration and modernization projects around the globe on both IBM mainframe and LUW target platforms. Each of these Natural transformation projects has been delivered on time, within budget and to the complete satisfaction of the client.
Automate the entire z/OS & z/VSE conversion to mainstream, open systems technology.
Liberate business systems from their dependency on non-strategic, legacy technologies.
Enable business applications to be integrated with state of the art components.
Explore multiple transformation solutions from COBOL to Object-Oriented languages or to another COBOL compiler technology.
Migrate your BS2000 mainframe to functionally-equivalent target applications that can be easily maintained.
Use automated tools to shorten re-development and testing cycles, reduce costs and minimize risk during your project.
Achieve an automated conversion of legacy Assembler to functionally equivalent C# or Java programs that run on Open Systems.
Get in touch with our experts and learn how automated migration and testing can support your project.