Many of today’s applications that were developed in COBOL are still mission-critical and continue to deliver significant benefits. Nevertheless, the organizations that rely upon them are often faced with increased licensing and maintenance costs, skill shortage, or simply end of support for the technology that served them well for many decades.
Astadia's COBOL transformation solutions provide the opportunity to liberate these valuable and reliable business systems from their dependency on compiler technology and convert them to Object-Oriented languages such as C# or Java, or to another COBOL compiler technology, which also often makes good business sense.
Whether on mainframe or off mainframe, companies might face critical challenges with their applications running in COBOL.
1. They soon will be facing a skillsissue. Many COBOL programmers are approaching retirement. Although it is notvery difficult to train people in COBOL, history has shown that young talented programmers and developers are not overly enthusiastic about this prospect.
2. They are locked-in to a non-flexible environment, often subject to a kind of subscription-based payment scheme, and reducing the costs and lock-in has become an objective.
There are anumber of options available, and the best choice will depend on the concrete as-is situation and the challenges faced:
1. Stay with COBOL, but move out of the current expensive environment and run an affordable COBOL compiler without runtime subscriptions. The applications can even run natively in a containerized environment in a cloud architecture (on prem or public).
2. Transform COBOL in another language all together. This can be Java or C#, and allows you to run the applications natively in a containerized environment in a cloud architecture, on prem or public.
3. Transform COBOL to Java or C# (Option 2), but allow developers to continue to develop and test in COBOL via Astadia’s Visual Studio Project plug-in CobolBridge.
All three options are possible, with plenty of proven successes for companies currently running COBOL applications on mainframe or running COBOL applications off mainframe.
For those that start on mainframe, there is yet another alternative, and that is to move from COBOL to Java on mainframe, with two options even:
4. Transform the COBOL to Java and run on z/Linux
5. Transform the COBOL to Java and stay on z/OS
Organizations taking this approach can also use CobolBridge as a (temporary) solution to allow developers to continue to develop and test in COBOL, while actually compiling Java on mainframe.
Choose the migration solution best suited to your platform's capabilities, complexity of data structures, and urgency to transform.
Download the COBOL Transformation Options White Paper.
Transform all code allowing your team to start working natively in Java/C# or use another COBOL compiler.
Combine maintaining COBOL code with executing Java/C#, allowing your developers to make the transition to Java/C# gradually over time, for example team by team.
> CobolBridge transformation options
Explore our z/OS & z/VSE Migrations Options
Explore our Assembler Migrations Options
Explore our Adabas-Natural Migrations Options
Explore our BS2000/OSD Migrations Options
Explore our CA IDMS & CA ADS Migrations Options
Explore our COBOL Migrations Options
Explore our EGL Migrations Options
Explore our UNISYS Migrations Options
Get in touch with us
Get in touch with our experts and find out how Astadia's range of tools and experience can support your team.contact us now