The enduring prevalence of COBOL (Common Business-Oriented Language) in mission-critical applications poses a challenge for modernization efforts, particularly in the transition to Java. This paper explores the intricacies of converting COBOL to Java, emphasizing the avoidance of JOBOL—a term coined for Java code that retains procedural characteristics without embracing object-oriented principles. The discussion includes strategies for data-oriented conversion, dead code elimination, and the adoption of event-driven approaches to ensure a successful transition that leverages the full potential of Java.
Introduction
COBOL, an acronym for Common Business-Oriented Language, has been a stalwart in the programming world, particularly for business applications, since its inception in the late 1950s. Despite its age, COBOL remains a critical component in many organizations, with millions of lines of code still in use for core mission-critical applications. However, as technology advances, there is an increasing push towards modernization, with Java being a popular target language due to its object-oriented nature, robust ecosystem, and wide adoption in contemporary software development.