MicroFocus COBOL Migration - Specific issues
MicroFocus COBOL applications tend to be very close to IBM COBOL Applications.
The primary difference is enhancements in Screen handling, and a wrapper layer around Operating-System calls.
|
COBOL SCREEN SECTION and Conversational programs
MicroFocus COBOL provides and additional SCREEN SECTION allowing design of static screens.
Such screens tend to be used within Conversational programs, designed for a "client-server" type deployment.
SoftwareMining converts such Conversational applications to a Application-Server architecture.
MicroFocus COBOL also regularly uses control characters to control screen operations (e.g. Blank Screen).
Where possible, SoftwareMining translates these control characters to statements which describe the operation (e.g. blankScreen() method).
|
|
Migration of MicroFocus COBOL code with OS API's
MicroFocus COBOl provides numerous OS centric API's for handling. After migrating such code to Java or C# -designed for Application Server, many of these calls will no longer be required. As such , each call needs to be individually evaluated.
|
MicroFocus COBOL 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
|
Microfocus COBOL Migration, Modernization and Re-hosting References
IBM CICS
Pseudo Conversational Transactions (Wiki)
Pseudo Conversational Transactions (IBM)
|
For further information please contact sales@softwaremining.com
|
