COBOL with Java & .NET
COBOL - Back to the Future
Despite being declared dead many times, applications written in COBOL are still in widespread use globally but have to meet ever increasing requirements. Making sure these applications stay economic and fit-for-purpose poses major challenges for businesses. Modern compilers offer wide ranging, remarkable opportunities in terms of performance and modern technology and platform integration for those using COBOL with Java & .NET. We support you to choose solutions that suits you. In doing so, we ensure your applications are goal oriented and continue to meet your expectations.
Advantages:
COBOL with Java & .NET: the Market Situation
Globally, at least 80% of business transactions still use COBOL. Developers have written over 220 billion rows of COBOL source code since 1959. COBOL is deeply embedded within many businesses and contributes significantly to smooth business as usual operations. While various technologies have been added to and built around COBOL applications over the years, at their core the existing COBOL logic remains.
COBOL is primarily process oriented. A host of newer, object oriented programming and scripting languages offers advantages for new systems and system architectures. Nowadays, developers can make use of many modern tools for different development tasks. This all means that the likes of Python, JavaScript, C, C# or Java have become the new standard for young programmers. On top of this, many experienced COBOL-programmers are nearing their retirement age and cloud-based container applications appear to be the future. In the face of this, one key question facing businesses is: how can core COBOL applications be run and maintained in future, and how can their continued adaptability to new requirements be ensured? In principle, businesses can choose from three options:
-
- use of standard products
- migration of core applications to a new programming language
- retention and modernisation of COBOL applications
All three solutions have their own limitations and challenges when it comes to COBOL with Java & .NET. The most risky is the use of standard products. Because historically grown applications are essential to smooth business operations, applying standard products to these can alter the implementation of processes to such a degree as to affect business as usual. In a worst case scenario, such processes could get lost – but either way, business operations are put at risk. Below, we take a closer look at the other two options for COBOL with Java & .NET.
COBOL with Java & .NET: the Challenges
All three options come with considerable challenges, and all require changes to the core application and all a lot of testing and effort. The easiest, in terms of complexity and effort required to implement it, is changing the COBOL compiler. As a business, you will likely face the following challenges when it comes to making decisions about your COBOL with Java & .NET:
-
- not to alter the core application’s key functionality
- to guarantee that current requirements continue to be met
- to enable modern technology integration
- to support developers with modern tools and IDEs
- to objectively assess feasibility, risks and the resources required
- to enable a potential, step-by-step replacement of COBOL
- to enable existing application systems to meet new requirements
Solution and Approach
The right solution always depends on your individual requirements and goals.
Success can be achieved in different ways when it comes to migrating a core COBOL application to a new programming language. In the case of a full language migration, the use of modern COBOL cross-compilers is usually the most secure route and has the advantage of simplifying the process. Two potential sub-routes are available for this: either an incremental one, or a “big bang”. While an incremental approach is preferable in most cases, both have advantages that depend on circumstances and requirements. In both cases, using a COBOL cross-compiler or transpiler is key. A transpiler translates existing COBOL source code into the target language during the compilation process. This makes it easier to embed the code in and communicate with application modules in different languages, for instance Java. You will still program in COBOL and artefacts are produced in the envisioned target language. The produced source code remains sequential and is transformed into an object oriented language. Guaranteeing language compliant development in the target language requires some specific adaptations to existing software structures. We support you through all of these adaptations. You can find more information about our other solutions here:
If you want to retain COBOL while modernising the application itself, you will find the challenges are less complex than those you may face in a language migration solution. However, you may find that changing from one compiler to another is worth the investment – both in terms of finances and in terms of technology. Numerous modern COBOL compilers with a variety of specifications are already available. Each comes with its own advantages and disadvantages. We are an experienced distributor of COBOL compilers and know each of them well. Drawing on this knowledge, we help you select the right compiler for your needs concerning COBOL with Java & .NET.
Why EasiRun
As an experienced IT services provider that offers consulting, development and solutions, we have over 40 years of legacy application project expertise to benefit you. We offer an extensive portfolio of COBOL compilers that meet an impressive array of modern IT requirements. We draw on best practice approaches, a combination of migration tools and products, and an international network of excellent partners to offer you the experience, professionalism, skills and attention you need to plan, implement and verify your change of compiler.
In all our COBOL with Java & .NET projects we use a reliable project management approach that ensures your modernisation project is transparent, completed on time and cost, and meets all agreed milestones.
