Automated Code Conversion delivers a modern application and data tier with 100% like-for-like functionality as compared to the legacy application, based on fully maintainable open systems. We use our DBShuttle and Zulu technologies to convert applications from Natural to COBOL, Java, or C#.
Automated Natural Conversion:
- Uses mainframe applications as the basis for new off-mainframe applications
- Produces object-oriented applications that are easy for your C# and Java teams to maintain and enhance
- Produces easily maintainable COBOL, familiar to mainframe developers but without the licensing headaches of Natural
- Focuses on fast and accurate code conversion that guarantees like-for-like functionality
- Great for applications moving from Natural to COBOL, Java, or C#, with minimal capability extension planned
The Automated Conversion process takes Natural source code and generates fully functional web applications. The process requires no “post modernization” manual fixes – the code generated is ready for deployment and maintenance.
Prior the Natural conversion, the ADABAS to Relational mapping must be determined. This mapping can be changed by editing a matrix (generated by the Modern Systems Modernization Tool) or by using the Modern Systems DDM Editor. Changes to the Default Model include denormalizing fields, placing fields in different tables, different column names, functions to build field values, etc.
The new code has the original Natural source embedded in it as comments, making it easy to find business logic when one is familiar with the structure of the application. The code is pure Java®, C#, or COBOL code and object-oriented conversions are maintained by use of Microsoft Visual Studio (.NET) or through any of the Java IDEs now widely available such as Eclipse, IntelliJ, NetBeans, etc. The full functionality of the IDE can be used to refactor, replace, rename etc.
The Modern Systems Migration Tool emits modern web pages in the form of Java Server Pages (JSP) or Active Server Pages (ASP .NET) that implement the user interface. There is one page for each map and one page for each INPUT statement in the application that does not use a map. The JSP pages use a Custom Tag Library, and the ASP pages use a Custom Control (ASCX) to implement the functionality of Natural’s map processor. During the modernization process, the maps are also emitted as XML documents, one document per map. Each XML document contains the entire map in simplified form which provides a repository for tools that operate on maps. One of these tools is the Modern Systems Map Editor. This utility enables editing of maps in a comfortable drag-and-drop setting that is superior to the original Natural Map Editor. Developers can move items around the screen by dragging them, double click on an item to set attributes, set a customer renderer for a field such as drop-down list or date picker, or write a customer renderer.
The automated conversion solution also addresses the replacement of the utilities that are typically part of existing mainframe environments, including Entire Operations, Entire System Server, EntireX, Natural Construct, Natural Security, and Com-plete.