Natural conversion

Natural conversion to Java or .NET

FreeSoft’s CodeLiberator converts complete Natural applications either running currently on Mainframe or open system to the Java or .NET stack including the business logic, data access and user interfaces. The migrated application provides the original equivalent functionality both in on-line and batch processing. The daily business is not influenced by the Natural to Java migration project as the impact on end-users is minimal, the converted Java system works the same way and provides the same services and user experience as the legacy system.

Conversion of Natural on-line processing

All Natural on-line processing either the classical 3270 MAP and inline processing, or the Dialog GUI is converted to the target user interface technology by CodeLiberator that can be thin-client web application or some GUI during Natural to Java conversion. The converted Java application is hosted in a Java enabled application server that might be open source (Tomcat) or some more robust middleware (IBM WAS; WebLogic; etc.). For the web application we support more architectural options like some frameworks e.g. JSF or preferably some very thin and light architecture like platform independent HTML/JavaScript (utilizing reactive programming). If a more rich GUI is defined as the strategic platform for the Natural conversion project, LiberatorWorkbench is able to convert to JavaFX that communicates with the application server via http.

Conversion of Natural batch processing

The Natural batch programs are also converted to Java and might be packaged in simple Java archives or some specific containers after Natural conversion. The Java batch programs expect the same input parameters that the Natural programs had earlier and execute the same logic and data processing in the relational database, so the Natural to Java conversion does not change input/output of batch processes. Any input and output files (WORK; PRINT) are fully identical with the original ones so the impact on operational environment (data export/import; printing; etc.) is either entirely eliminated or minimized (e.g. if clients moves from EBCDIC to ASCII when migrating Natural to Java).

Conversion of ADABAS database access in Natural

As the underlying ADABAS database is migrated to a relational database engine, the data access is properly converted to a separate DAO layer that is RDBMS agnostic so it can run against Oracle, DB2/UDB, MSSQL or other relational engines that stores the migrated ADABAS data. The data access statements of Natural (FIND; READ; HISTOGRAM; GET; UPDATE; STORE) are supported by our Natural to Java code conversion solution and framework with 100% coverage, also respecting looping, child (MU/PE) handling and anything else related to data storing e.g. null suppression, etc. Transaction processing of the original legacy application is implemented in our Natural conversion solution of course to preserve integrity of data.

Migrating Natural language specific elements

All aspects of the Natural programming and run-time environment are fully supported by the LiberatorWorkbench conversion framework to implement the original identical business functionality of programs in the Java technology stack. Statements that has no direct equivalent in OO languages like Java but are heavily used in Natural coding among others REDEFINE; MOVE/BY NAME; COMPRESS,COMPUTE ROUNDED etc. or special data types are implemented with the same correctness and functionality in the converted Java application. Without these implementations an automated Natural conversion solution is not able to produce a functionally correct and precise application migration for any business application so any language conversion solution must support these. The syntax and structure of the code is straightforward and simple to follow both for new developers and Natural programmers as well. CodeLiberator can use several design patterns and rules for Natural to Java conversion so we can adjust the syntax of the resultant code to your requirements. We also provide turn-key solution to other Natural specific infrastructure elements like replacing EntireX integration, user exits, etc.

To find out how our Natural application migration solution works in real life projects, check one of our customer stories where 5 million Lines of Code Natural had been migrated successfully to Java with LiberatorWorkbench.

For further details about automated migration of ADABAS databases to relational engines like Oracle, MSSQL, DB2/UDB, etc. please visit the ADABAS migration page.