SoftwareMining •
COBOL to Java & C#
• Predictable & Repeatable
SoftwareMining provides automated, rule-based tools for converting Unisys MCP and Burroughs COBOL applications into maintainable Java or C# source code. The tools support COBOL business logic, DMS-II database operations, record navigation and status handling. DMS, DMS-II and DMS-2000 database structures can be mapped to relational SQL tables as part of the modernization process.
Unisys COBOL is broadly based on COBOL 74 and COBOL 85 standards but also includes platform-specific language features, screen handling, database interfaces and APIs associated with the Unisys MCP environment. SoftwareMining identifies supported platform dependencies during application analysis and converts them into corresponding Java or C# implementations while preserving the application's business logic and functional behaviour.
| Unisys MCP Feature | Modernized Java / C# Implementation | Comments |
|---|---|---|
| DMS, DMS-II & DMS-2000 | SQL database schema and generated DAO classes | Database structures are analysed and can be mapped to relational SQL tables while preserving the application's data model. |
| FIND | Equivalent keyed database retrieval | Primary key lookups are translated into equivalent Java or C# data-access operations. |
| FIND FIRST / LAST | Ordered database queries | Record ordering and navigation semantics are preserved using generated SQL and data-access logic. |
| FIND NEXT / PRIOR | Cursor or iterator navigation | Sequential navigation through record sets is maintained in the translated application. |
| SET ... TO BEGINNING / ENDING | Navigation state management | Database positioning statements are preserved using equivalent Java or C# navigation logic. |
| DMSTATUS Handling | Status and exception processing | DMS status codes are translated into equivalent status handling or exception processing while preserving application behaviour. |
| Database Sets and Indexes | Generated relational indexes | Primary and secondary access paths are preserved using generated SQL indexes and data-access methods. |
| Screen Processing | Modern HTML user interface | Screen definitions can be modernized into browser-based interfaces while preserving the original workflow. |
| Business Logic | Java generated using predefined, repeatable rules, with optional C# | COBOL calculations, business rules and processing logic are converted using predefined, repeatable rules and validated against the original application. |
| Deployment | Java application server or ASP.NET | The translated application can be deployed on modern server infrastructure, either on-premises or in the cloud. |
Unisys COBOL programs often utilize DMS, DMS-II, or DMS-2000 database systems and their associated APIs.
The first step in SoftwareMining's migration process involves parsing the DMS database schemas using our translator. This process generates COBOL copybooks that represent the Data-Sets.
These copybooks are then utilized by the COBOL to Java/C# Converter to produce:
For instance, a record named INVOICE-RECORD will be converted into an SQL table called INVOICE_TABLE, containing all the fields defined in the COBOL structure. Additionally, an Object-Relational class, InvoiceClass, will be generated to handle database communication between the translated application and the SQL database.
The API simplifies database access through statements like CREATE, STORE, LOCK, FIND, and SELECT, ensuring efficient interaction with the new database.
Furthermore, additional UNISYS-specific APIs will be supported through SoftwareMining libraries, ensuring seamless integration and compatibility.