French Portugese German Danish Dutch Spanish Italian Japanese

Breathing life into
legacy applications

       Home > Platforms > Unisys

UNISYS MCP and Burroughs COBOL Migration

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. These database are not based on a CODASYL designs, and are used as a replacment for VSAM structures.
SoftwareMining Translation Toolkit can use the COBOL Listings (which include the "Cobol" version of database schema) in translation of the DMS schemas to a Relational Database. The system will also generate Object-Relational data access classes for each of the tables. These classes will cater for all future database accesses. For example, a record called INVOICE-RECORD will be translated to SQL Table INVOICE_TABLE (containing same fields), 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.
SoftwareMining CORECT Translates DMS / DMS-II library calls to a Java Persistence Framework - utilising SQL databases. DMS / DMS-II Database scripts are re-engineered into Relational-Database.

Modernization of UNISYS LINC and WFL

SoftwareMining can offer migration of LINC to Java though associated partners.
In such cases, translated LINC and COBOL applications will continue to communicate to offer the same functionality.
Later versions of LINC can also be ported to Unisys's AB-Suite development enviroment, and work in a Microsoft environment. This would pave a path for integration of C# translations of COBOL applications

UNISYS COBOL Migration, Modernization and Re-hosting References

Unisys Burroughs . Unisys DMSII .

UNISYS COBOL MCP CLEARPATH DMS COBOL Migration, Modernization and Rehosting Project Phases

The translation of to Java or C# applications involve
  • Asset Management: Identify all the artifacts required for translation .
  • (Optional) Business Rule Extraction.
  • Translate to target language
  • Database and Data Migratation
  • Migrate JCL / WFL / CL
  • Creation and Population of Test Database
  • System acceptance testing
  • System acceptance testing
  • User Acceptance Testing
  • (Client): Interation 2 Improvements: Screen Redesign, SOA Integration, Cloud Deployments, Coding Improvements and cleanup

  For further information please contact sales@softwaremining.com


 News:


2010 May State of Maine Revenue Services Tax Office: New Java system goes live

2010 Apr COBOL to Java transformation now supported on IBM z/OS and System Z

2009 Computer Weekly Magazine article - outlines benefits of SoftwareMining's Automatic Migration.

Short Cuts:


Contact Us
Online Technology Videos
Legacy Modernization Blog

Brochures & White Papers

COBOL to Java/C# Transformation White Paper

Business Rule Extraction Brochure

Manual Rewrite vs. Automatic Transformation: Risks and benefits.


 

  © 2010 , SoftwareMining. All Rights Reserved.
SoftwareMining Ltd. Reg. Eng. 02733107. Reg Offices: 8b Accommodation Road, London NW11 8ED, United Kingdom.

http://www.softwaremining.com