The Application Transparency Platform® (ATP®) is a revolutionary Natural replatforming and ADABAS conversion solution that provides an end-to-end strategic pathway for lower licensing costs, higher productivity, and full preservation of legacy assets and business rules. Organizations looking to move away from Natural can use ATP to automatically convert syntax to COBOL, Java, or C# on demand. As an alternative to the re-engineering and conversion solutions available for Natural and ADABAS, ATP dramatically reduces the time frame for the replacement cycle and accelerates your return on investment.

The ATP process begins with ADABAS conversion into the relational database of your choice — DB2, SQL Server, or Oracle — and processes Natural applications using ATP Language (ATPL™) on Windows. The ADABAS conversion is automated. ATP® enables Natural replatforming seamlessly from the mainframe environment to a more economical and more robust ATP® environment, thus reducing maintenance/licensing fees and mainframe workload. Since ATP® interprets and executes each Natural command, the Natural applications can execute against the new relational database without changes to the Natural syntax.

In addition, ATP® includes a full-featured UI-based development platform that includes Natural code analysis, flow diagramming, impact analysis, pattern matching, version comparison, and interactive debugging. The existing Natural development team can continue to develop and maintain applications as they always have with the support of modern development tools.

Retaining Natural syntax may be the final modernization goal for some organizations. For others, it might be a step in a phased approach to move away from procedural code and pre-relational databases altogether. ATP® is designed to support customers regardless of how far down the modernization path their migration effort takes them.
Benefits of Natural Replatforming & ADABAS Conversion with ATP
  • Reduce or eliminate mainframe costs with a short-term Natural replatforming project that provides fast ROI
  • Reduce expensive maintenance/licensing fees
  • Retain Natural applications, expertise, and skilled teams
  • Upgrade technology and computing platforms without materially impacting the business
  • Replace ADABAS with industry-standard, easy-to-access relational databases
  • Add off-the-shelf RDBMS reporting, query, and business intelligence tools
  • Add on the eavRPM® tool assisted re-engineering workbench so Natural development teams can begin the transition to native web processing

ADABAS Conversion with ATPconvert™

The fully automated ATPconvert™ toolset is the engine behind ADABAS conversion into the relational database technology of your choice: SQL Server, Oracle, or DB2. The ATPconvert process includes the generation of the new database definitions, population of the tables with the current ADABAS data and allows for data cleansing activities.

After Natural replatforming, the original code seamlessly processes against the new relational databases without modification using the ATP runtime. As an added bonus, modern web applications can access the relational databases directly, allowing the organization to benefit from industry-standard SQL-based reporting, query, and business intelligence tools.

Seamless Natural Replatforming Using ATPlanguage (ATPL™)

Natural syntax is not converted for the ATP execution and changes are not required to access the new relational databases. Natural developers can continue to maintain and enhance the applications in a language they are accustomed to.

Replatforming Solution Options

Modern Systems' history has given us the ability to fully understand many vendors' programming languages at the true binary level, allowing us to interpret and execute the programming language natively within our own developer and end-user environment. The ATP® solution brings with it a full development platform, enabling application documentation, debugging, dual run-mode execution, version control, and enhanced features beyond the original programming language environment. If you're looking to move away from your current licensing agreement but want to retain your Natural applications in their current format, ATP provides two paths.

Mainframe Solution
The mainframe solution involves ADABAS Conversion to DB2 for z/OS. This relational database environment allows you to continue using your mainframe resources to host your data and databases. Natural replatforming is achieved by importing the applications into ATP to run un-changed against the new relational database. Batch options include conversion of the batch Natural programs to COBOL running on your mainframe or re-engineering your batch reporting to utilize standardized reporting packages.

Off Mainframe Solution
The off mainframe solution involves a one-time ADABAS Conversion to Oracle or SQL Server hosted on an appropriate system. Natural replatforming is achieved by importing the applications into ATP to run un-changed against the new relational database. Batch options include conversion of the batch Natural programs to or C# or re-engineering your batch reporting to utilize standardized reporting packages.

On-Demand Automated Language Conversion with ATP SaveAs

Application Transparency Platform (ATP®) supports automated conversion to C#, Java, or COBOL through a simple right-click, SaveAs function. This is an industry first, bringing automated conversion to the end user. Using this feature, it is possible to maintain the Natural, but choose to have the actual syntax converted to C#, Java, or COBOL at the time the syntax is saved by the developer. Once saved, the newly converted code is functionally equivalent to the legacy Natural syntax. This feature enables the best of both worlds; re-use the developers’ existing skill sets in Natural, and their extensive knowledge of the applications, while deploying as C# or Java (providing the benefit from the deployment of web apps running natively) or COBOL (where it is possible to execute the applications on any platform).
ATP Developer Features
The ATP development platform provides features beyond those available to Natural developers today. With ATP®, Natural developers can document their applications, debug processing at run-time, execute in dual run-mode, benefit from version control, and continue Natural development and maintenance using enhanced features and a UI.

  • ATPL Editor: Edit the legacy language using the same syntax. Access point & click features such as copy & paste, or save snippets of commonly accessed code for future use
  • DDM, FDT, and Data area Editor: View the original syntax or edit in the easy to use tables
  • WYSIWYG Map Editor: Drag and drop visual objects to build screens while source code is generated in the background
  • Full-Featured Interactive Debugger: Set breakpoints, watch variables, and step through the functional code for trouble shooting
  • eavZoom: Jump to the currently executing line of code in the documentation for further exploration including flow charts, code paths, impact analysis, and enterprise views
  • Dual Runtime Mode: Try out a new feature or run the original version of code without committing changes
  • Runtime Deployment Tracking: Easily generate different runtime environments for production, Q&A, development, etc.
  • Version Tracking: View the history of when a program was changed & who made those changes
  • Internal or Active Directory Security Support: Users only see what they are authorized to see
  • Local and Remote Program Execution Trace: Monitor lines of code as executed to find issues arising from user interaction
  • Testing Monitor: Know which lines of code have been tested
ATP Dual Runtime Demonstration
ATP Debug Feature Demonstration

Job Execution with eavJES

Our eavJES batch execution suite, an ancillary toolset within the ATP® replatforming environment, provides a job execution system for organizations who want to preserve their JCL and PROCS, and continue to maintain them even when they move off the mainframe.

eavJES provides the ability to replatform JCL and PROCS with very little change. Developers maintain the JCL and PROCS according to existing JCL rules. Execution results in the same actions, cataloging, restart, and recovery as on the mainframe. The Catalog is constantly monitored and maintained during job execution and can even allow command-line manipulation of datasets.

Initiator setup allows jobs to be classed and executed as they are on the mainframe. Job classes can be given different priorities with a limited number of initiators for each type. Message class setup allows output for a class to be automatically transitioned to PDF output or to email, Load Libraries can be sequenced for each eavJES environment so that the proper load modules are executed for that batch “region”, and storage units can be defined to reflect the different storage types that were used in the original mainframe environment.

eavJES also contains a function that allows jobs to be pre-scheduled for submission at a specific time or upon an occurrence of a pre-defined event. Additionally, eavJES Listeners provide the ability for other processors to submit a batch job remotely, in the same manner that the mainframe provided internal reader submission. For maximum visibility, the eavJES monitor provides operations and development teams with the ability to monitor jobs, change priorities, review outputs, and perform other batch management.

Modernization with Zero Impact to Business Users Thanks To ATPaccess™

ATPaccess™ enables Natural replatforming and ADBAS conversion without affecting the business user experience. The functionality remains the same, so no training is required. All screens retain the same user-created look and feel. Even the keystrokes, tabbing, and PF-keys remain unchanged. It is easy to update the default colors and backgrounds, but user interface changes are optional.

In addition, developers gain a method for communicating with users via an application portal and message board. Notices can be issued on a per entry point basis so maintenance time frames or other user messages can be customized for each application.

ATP Reduces Risk, Reduces Costs, & Eliminates Big Iron for Good

Numerous factors are driving companies away from legacy platforms, but change can be risky. Replatforming is a good way to move to distributed platforms, eliminate licensing charges, and retain legacy source code, allowing existing developers to continue to work with programs they are familiar with in the syntax they know. Be sure to browse the myriad of resources we have available below on Natural replatforming and ADABAS conversion with ATP.

ATP Received Microsoft's Platform Modernization
Technology Achievement Award 2012

Platform Modernization Technology Achievement Award

Additional Resources

  • You Can Teach An Old Dog New Tricks - This whitepaper incorporates industry analysis, direct customer feedback, and over 30 years of project experience to help you understand the mainframe modernization ecosystem and how replatforming Natural applications with Modern Systems is the fastest, least costly, and lowest risk option for extricating your organization from reliance on the mainframe and Software AG.
  • Save Your Environment the Natural Way - This whitepaper outlines how firms are empowered to take a phased approach to modernization using Modern Systems’ tools to replatform and later migrate to COBOL, Java, or C#, removing the common risks many executives and application developers cite as reasons to stay with their current technology. It also describes how these tools enable organizations to break the ties that bind them to expensive fees.
  • Avoid Natural Disaster: How to Replatform ADABAS & Natural - Replatforming Natural applications is a good way to move to distributed platforms, eliminate Software AG licensing charges, and retain Natural code syntax.
  • Modernizing Legacy Applications for Blended ERP - How Modern Systems can help customers leverage "Blended ERP" for easier customization, reduced cost, and reduced risk.
  • How To Bring DevOps to Modernized Mainframe Applications - Improve deployment frequency, lower failure rates, shorten lead time between fixes, and speed mean time to recovery by bringing DevOps to modernized mainframe applications.
Case Studies
Other Related Content
  • eav Datasheet - Enterprise Application Viewer (eav) is an application understanding and documentation tool that works alongside ATP. Visit the product page here or download an evaluation copy here
  • eavRPM Datasheet - Rapid Program Modernization (RPM) is a tool-assisted reengineering product that works alongside ATP. Visit the product page here.

Heads up! This website is no longer being updated as of 2022. For the most up-to-date information on Advanced's modernization services and/or for any enquiries, go to