UNISYS MCP and Burroughs COBOL to Java / C# Conversion

UNISYSs dialect of COBOL is fairly close to ANSI COBOL 74/85 Standards.
The main differences is the extensions to COBOL language, Screens definitions, use of DBMS , DMS Database and API.

DMS, DMS-II, or DMS-2000 Unisys COBOL programs typically utilise DMS, DMS-II, or DMS-2000 database system and API. The first step in SoftwareMining's migration process is for the translator to parse the DMS database schemas, and generate COBOL copybooks representing Data-Sets. These copybooks will used by the COBOL to Java/C# Converter to produce: SQL Schema The new tables will contain the same fields as those defined in the Schemas Object-Relational Data-Access-Objects (DAO) the translated programs will access the SQL table via these DAO classes For example, a record called INVOICE-RECORD will be converted to SQL Table INVOICE_TABLE (containing all the fields defined in the Cobol structure), and Object Relational class InvoiceClass which manages all database communication between the translated application and database. The API simplifies database access thru CREATE, STORE, LOCK, FIND, SELECT type statements. Additional UNISYS API will be supported by a SoftwareMining libraries.

UNISYS COBOL Migration, Modernization and Re-hosting References

Unisys Burroughs . Unisys DMSII .

UNISYS COBOL MCP CLEARPATH DMS COBOL to Java/C# Migration Project Phases - Further reading

• Managing COBOL to Java / C# Conversion Projects
• Gradual migration of COBOL applications to Java: one piece at a time - reducing costs and risks.

  © 2023 SoftwareMining is a trademark of Software Modernization Technologies Ltd (UK). Registered in England company no: 07300248. Reg Offices: 79 Stevens House, Jerome Place, Kingston Upon Thames, KT1 1HX, United Kingdom.