Natural into Java Transformation
Demystify the migration process with a step-by-step look at the way Natural can be transformed into working, maintainable Java code. Why Migrate Your Mainframe?
High (and continuously increasing) maintenance and runtime fees for the existing Natural products
The shrinking availability of Natural developers and lack of interest in Natural from new developers
Lack of an easy transition path from the mainframe version of Natural to its Linux, Unix, and Window
Java offers answers to all of the above concerns:
- Maintenance fees are negligible when compared to Natural, or even nonexistent depending on the choices made
- Even though there is no universally accepted barometer to measure the popularity of various programming languages, there is no denying that Java is considered one of the most widely-used programming languages today. In addition, the design of Java aims for programmer portability, for the vast range of developers familiar with C, C++, and C#
- Although the catch-phrase “write once, run anywhere” may be somewhat disputable, Java certainly is extremely portable
Next to that, moving to Java also means:
- Enabling the use of a state-of-the-art IDE, with extensive debugging, refactoring, profiling and (unit)testing support
- Enabling the use of thousands of (third-party) libraries, covering almost all imaginable computing needs: database interaction, mail/ftp/http/… communication, parsing, xml processing
- Enabling the use of modern application architectures including the use of an application server, web front‑ends, SOA, cloud-deployment
Send me the whitepaper
Thank you! Please wait redirecting...