SoftwareMining •
COBOL to Java & C#
• Predictable & Repeatable
COBOL-to-Java and COBOL-to-C# Converter supports the migration of Micro Focus COBOL applications into maintainable Java or C# source code using automated conversion. It operates within the customer's own infrastructure.
Many Micro Focus applications originated on IBM mainframes and retain dependencies such as CICS , JCL, VSAM and embedded SQL. Others include Micro Focus compiler directives, runtime services, file handling and database interfaces. SoftwareMining analyses both inherited and Micro Focus-specific dependencies while preserving established application behaviour.
Many Micro Focus COBOL applications were originally rehosted from IBM mainframes and continue to follow COBOL 74 or COBOL 85 conventions. They may also retain mainframe-derived dependencies such as CICS services, JCL batch processing, VSAM files and DB2 embedded SQL.
Applications developed or extended after rehosting may additionally use Micro Focus compiler directives, runtime services, screen handling, operating system interfaces or other platform-specific features. Application analysis must identify the dependencies actually present before conversion begins.
The following resources describe relevant modernization patterns:
Rehosted applications may still contain CICS-compatible transaction processing, JCL, VSAM access, embedded SQL and other structures inherited from the original mainframe system. SoftwareMining identifies these dependencies and converts supported features into corresponding Java or C# implementations.
Some Micro Focus applications use SCREEN SECTION definitions, terminal-control characters or proprietary screen-handling services. SoftwareMining analyses these interactions and maps supported screen behaviour to components appropriate for the target Java or C# application architecture.
For example, terminal-control operations such as clearing a screen can
be represented by readable target-language methods such as
blankScreen().
Micro Focus applications may call operating system APIs, runtime services or external libraries. Each dependency must be analysed to determine whether its behaviour remains necessary in the modernized application. Required behaviour can be replaced with an equivalent Java or C# implementation, while obsolete dependencies should be removed only after analysis and testing.
For a broader comparison of rehosting, replatforming, automated source-code conversion and other approaches, see the Comparison of Mainframe Modernization Strategies .
