Datafile Strategies for Migrating from COBOL to Java and C#
SoftwareMining's strategy for migrating from COBOL to Java and C# ensures that SQL databases and Sequential files are retained.
In contrast, VSAM and Indexed Files undergo transformation into an Object-Relational architecture and are then incorporated into SQL databases.
Below is the detail of this migration approach:
Multiple File-Definition for the Same Datafile
Multiple programs within an application might designate varied structures (FILE-DEFINITION) for the same datafile.
This method works for Files but poses challenges when delineating database columns. Manually amalgamating such structures can be tedious and prone to errors. Automated identification and reconciliation of these definitions can be a cornerstone of successful migration projects.
Batch programs are often time-bound. Therefore, performance significantly shapes the design of the migrated Java or C# code. Factors greatly influencing the performance of migrated code include:
- Number fields: The translator should, where safe, convert COMPUTATIONAL formats to native Java data-types.
- Precision: Java BigDecimal should only be deployed when imperative.
- Removing redundant structures to reduce load time.
- Parallelization is more feasible with clear and maintainable code (Java/C# post-migration).
- REDEFINES: The translator's capability to identify and eliminate them.
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.