Modernizing Mainframe Applications with mLogica’s LIBER*M Framework

A financial services organization sought to modernize its legacy mainframe applications and data, transitioning them to Microsoft .NET technologies hosted on the Azure Cloud. mLogica, a leader in automated modernization solutions, was engaged by a global IT services provider to execute the first increment of this multi-phase initiative. The project aimed to migrate COBOL and Assembler programs, JCL scripts, and associated VSAM and sequential files to a scalable, cloud-based environment, leveraging mLogica’s LIBER*M automation and expertise.

The organization’s mainframe systems, while reliable, were costly to maintain and lacked the agility needed for modern operations. The applications—comprising of hundreds of thousands of COBOL, Assembler and JCL code—supported critical functions but were tied to outdated infrastructure. The project team faced:

• Technical Complexity: Converting diverse source types (COBOL to C#.NET, JCL to PowerShell, VSAM to Azure SQL) while preserving functionality.
• Timeline Pressure: Completing the migration within three months, from assessment to testing support, to align with the organization’s modernization goals.
• Risk Mitigation: Ensuring zero disruption to existing operations during the transition, with limited access to the source environment for validation.
• Collaboration: Coordinating responsibilities across multiple stakeholders, with clear delineation of tasks and deliverables.

mLogica proposed a fixed-price engagement, leveraging its automated tooling suite (LIBER*M) and structured modernization methodology. The solution included:

• Automated Migration: Converting COBOL and Assembler to C#.NET, JCL to PowerShell, and migrating VSAM and sequential files to Azure SQL or flat files.
• Phased Approach: A five-phase process—Project Preparation, Application Assessment, Source Code Migration, Pre-delivery Testing, and Testing Support—ensuring systematic progress.
• LIBER*M Framework: Providing a runtime environment and three years of Platinum-level maintenance and support at no additional cost, ensuring long-term stability.
• Collaborative Execution: The IT services provider and the organization led preparation and testing, while mLogica drove the assessment and migration, supported by a detailed RACI (Responsible, Accountable, Consulted, Informed) matrix.

The project launched in 2024, with a projected timeline of three months:

1. Project Preparation (Week 1): The IT services provider provisioned Azure-based Working and Staging Environments, while mLogica conducted a kickoff meeting to align teams and establish collaboration tools (e.g., Microsoft Teams, Jira).
2. Application Assessment (Month 1): mLogica analyzed the Cobol and Assembler lines of code and the JCL scripts, finalizing the scope and effort estimates. The IT services provider supplied asset collection files via Azure Files, resolving duplicates and missing components iteratively.
3. Source Code Migration (Month 2): Using LIBER*M, mLogica converted the codebase, delivering initial migrated applications for staging. Data migration from VSAM to Azure SQL was completed concurrently.
4. Pre-delivery Testing (Month 2-3): mLogica tested five representative test cases, validating iso-functionality against mainframe outputs using provided test artifacts.
5. Testing Support (Month 3): The IT services provider led comprehensive regression testing, with mLogica resolving migration-related discrepancies within a one-month window, delivering refined code drops.

The project achieved significant outcomes:

• Successful Migration: COBOL and Assembler programs, and all JCL scripts were fully migrated to C#.NET and PowerShell, with data in Azure SQL, meeting functional requirements.
• Cost Efficiency: Including three years of LIBER*M support, the project stayed within budget and avoided scope creep through rigorous change request processes.
• Timeline Adherence: The project was completed in three months, aligning with the aggressive schedule, thanks to automated tools and clear role delineation.
• Operational Continuity: Pre-delivery testing and comprehensive validation ensured no disruption to critical operations.
• Scalability: The Azure Cloud deployment positioned the organization for future increments, with LIBER*M providing a robust framework for ongoing enhancements.

• Early Collaboration is Key: The kickoff meeting and weekly status reports mitigated misalignments, reinforcing the value of proactive communication across distributed teams.
• Test Artifacts Matter: Delays in receiving comprehensive test cases underscored the need for earlier test planning, a dependency flagged in the SOW assumptions.
• Automation Accelerates: mLogica’s LIBER*M tooling reduced manual effort by 60% (estimated), proving automation’s efficacy in large-scale migrations.
• Flexibility in Troubleshooting: Limited source environment access necessitated creative workarounds, highlighting the importance of adaptable testing environments.

mLogica’s partnership with the IT services provider transformed the organization’s legacy systems into a modern, cloud-native solution, setting a foundation for future modernization phases. By blending automated technology with structured collaboration, the project delivered on time, within budget, and with zero compromise to operational integrity—an exemplar of successful mainframe-to-cloud migration in the financial sector.