Many organizations are still running large Natural applications that were developed more than 30 years ago. The high maintenance costs and lack of Natural developers is causing companies to look at Natural migration routes to more modern technologies.
Automated Natural Migration Without Functional Change
BluePhoenix’s Natural migration solution enables an automated migration of Natural applications to COBOL, Natural to Java, or Natural to C#. The Natural migration, or Natural modernization can be accompanied by an ADABAS migration to modern relational databases (such as ADABAS to DB2, ADABAS to Oracle, or ADABAS to SQL-Server).
Our Natural modernization solution provides an automated Natural migration to more modern architectures without functional change. Generated screens and windows use modern technology, while keeping the same look and feel (if required), which accelerates the users’ acceptance of the new application.
A complete solution is provided for migrating Natural applications, data models, and data. The end result is easy to maintain, well documented, and exists in a modern, lower-cost environment.
- Dramatically reduces license and maintenance costs
- Provides Web-based application look and feel (shorter users’ learning curve)
- Makes application enhancement easier
- Provides cost effective migration
- Eliminates the IT resources challenge
- Uses proven automated tools, thereby mitigating many of the project risks
- Supports data access to ADABAS, VSAM, IMS, DB2, SQL Server, or Oracle
- Handles all aspects of the Natural syntax including specific constructs such as REINPUT statements
- Handles all Natural objects including programs, subprograms, DDMs, maps, and data area types
- Supports both reporting and structured mode Natural
- Can be combined with the migration of COBOL to a relational database
- Multi-tier J2EE architectures with HTML/JSP client, Java core, and JDBC data access
- Highly maintainable—can be more easily enhanced in the new environments
- Allows customer-specific Natural migration options such as naming convention changes
- Support for JCL migration for a mainframe destination, or JCL to script for a Unix or Windows destination