LIBERM_Modernization

mLogica LLC

The LIBER*M Mainframe Migration Suite: The cost-effective solution for businesses tied down by legacy mainframes.

mLogica’s LIBERM capabilities help customers migrate mission-critical, enterprise legacy mainframe workloads, infrastructure, and data to Azure – eliminating risks while saving them time, money, and business disruption. mLogica combines automated software, proven methodologies, and deep technology experience to deliver legacy mainframe workload and mainframe migration projects in fixed-price mode. LIBERM provides several options to pursue your modernization journey: automation-enabled assessments, Rehosting to Azure compute and Azure managed databases, and Refactoring to C#.NET or Java. Accelerate Your Modernization by utilizing modernization solutions by innovation leaders in migrating and optimizing your legacy mainframe and iSeries workloads to a highly efficient Cloud infrastructure utilizing automated refactoring tooling suites.” • Price and service duration is variable depending on the mainframe and iSeries languages and data technologies, modernization approach, number & complexity of the mainframes workloads that are migrating to Azure. LIBERM handles a very broad range of mainframe and iSeries languages including COBOL, Assembler, Easytrieve, PL/I, CL and RPG. • Customers can expect fit-to-purpose deliverables for different steps in the modernization journey. For assessments, LIBERM automatically produces an “asset catalogue” summarizing legacy technical details and dependencies, a modernization roadmap that provides costs and timelines for the proposed modernization programme and a business case. For proofs of translation and proofs of concept, mLogica delivers rapid proof points to demonstrate the capabilities of LIBERM. For rehosting and refactoring, mLogica leverages LIBERM to deliver systems in Azure that are highly performant, highly available and functionally equivalent to the original legacy systems. The first step in most modernization journeys is an assessment. Building a modernization roadmap requires a comprehensive analysis of the legacy environment surrounding the source code including: -Reviewing the current state infrastructure, architecture and integrations -Analyzing mainframe data objects for size, growth and structure, e.g. copybooks, redefines, DDL, IMS DB DBDs, stored procedures, triggers, views, custom data types. -Assess the impact of mainframe modernization on dependent mainframe, distributed, partner and client applications. -Review and analyze major workflows and modernization objectives to consider business context • Pricing for assessments is dependent on counts of legacy code and data structures and on agreed objectives. Pricing for proofs of translation and proofs of concept is dependent on the scope and the delivery approach (i.e., executing in our secure lab vs. in the client’s network or Azure tenant). Pricing for rehosting and refactoring can be estimated at a “ROM” (rough order of magnitude) level using legacy metrics. Such a ROM is typically refined to a fixed price by performing an assessment. • Briefing discussion topics

  • Journey selection – the benefits of rehosting and refactoring for different types of workload and business scenarios
  • Demonstrations of refactoring and rehosting tools
  • Legacy data modernization – learn how LIBER*M maps non-relational data from IMS DB and VSAM to relational databases
  • Upskilling – explore how existing mainframe and distributed resources can maintain rehosted or refactored workloads

Workshop Agenda:- we don’t deliver “workshops” in the mainframe practice as we do in the distributed database practice. The complexity of legacy modernization scenarios drives us to push for a paid assessment as the initial formal engagement. We do briefings and demos, collect metrics, and produce an assessment SOW. This is the common pattern across many mainframe modernization vendors. I’m giving you a workshop agenda because I know you are keen to check off all the boxes, but I ask that you not publish this unless it is absolutely required by Microsoft. It doesn’t make sense for us to modify our service approach because Microsoft put a box on a form. Prior to an assessment, mLogica offers a 1-2 day workshop (depending on participant availability) to understand the modernization requirements at a high level and customize an assessment.

  1. Review relevant legacy footprint, enterprise architecture and staffing
  2. Modernization objectives discussion
  3. Modernization journey selection
  4. Data modernization scope discussion, considering historical and archived data
  5. Cloud architecture objectives and constraints
  6. Next steps – establish assessment scope and objectives
https://store-images.s-microsoft.com/image/apps.31226.bbf85371-4e14-4a47-8179-94b521173deb.c068d931-2272-408d-b5d3-e0c11a7dc240.d2a7c46f-584d-4655-8b2a-fd6812f2b012
https://store-images.s-microsoft.com/image/apps.31226.bbf85371-4e14-4a47-8179-94b521173deb.c068d931-2272-408d-b5d3-e0c11a7dc240.d2a7c46f-584d-4655-8b2a-fd6812f2b012
https://store-images.s-microsoft.com/image/apps.16251.bbf85371-4e14-4a47-8179-94b521173deb.c068d931-2272-408d-b5d3-e0c11a7dc240.d79e51a6-6bed-4c1b-bfa8-ec0a1aec9484