Mainframe Migration:

Methodology & Approach

Macrosoft Capability Statement

February, 2008

Contents

1. Overview

2. Migration Process Phases

2.1 Migration Analysis

2.2 Migration Design

2.3 Migration Development (Conversion)

2.4 Migration Installation (Live Migration)

2.5 Migration Monitoring (Post Migration Monitoring)

3. Automation and QA Utilities

4. Critical Elements in the Migration Process

5. Value-of partnering with Macrosoft in Migration

6. Development & Support Processes at Macrosoft

6.1 The Development & Deployment Process

6.1.1 Coordination of Different teams for collaborative development

6.1.2 The India Development Team

6.2 The Customer Support Process

7. General Database Migration Process

7.1 Database Schema Migration

7.1.1 Extract Database Metadata

7.1.2 Convert database Objects

7.1.3 Convert Queries

7.1.4 Implement Converted objects

7.2 Data Migration

7.2.1. Data Analysis

7.2.2 Data cleanup / enrichment

7.2.3 Conversion Study

7.2.4 Conversion Strategy Signoff

7.2.5 Conversion Tool Preparation

7.2.6 Mock Conversion

7.2.7 Conversion for Parallel Run

7.2.8 Conversion for Live System

8. Approach to COBOL, Easytrieve, and DATACOM/Ideal Migrations

APPENDIX-A: The Mainframe Migration Toolkit

APPENDIX-B: Macrosoft Profile

1. Overview

This document reviews Macrosoft experience and process methodology for migrating mainframe applications to client server environments (UNIX, Windows). Much of our work in this area has been done in conjunction with work projects such as Vestcom Migration. These applications handle critical data for numerous leading corporations. In all of these conversion efforts, our teams have worked side-by-side with client teams in effectively and securely performing these conversions. We have our own migration tools (MMK) as described below, as well as expertise in using industry standard tools such as MicroFocus Revolve, Micro Focus NetExpress, Oracle Migration Workbench, SQL Server Migration Assistant, IBM Migration Toolkit, etc.

We have strong and long standing partnerships with Microfocus, Microsoft, Oracle and IBM, which help us in adapting their products on Unix/Windows for mainframe migration. We are members of “Mainframe Migration Alliance (MMA)” and “Mainframe Transformation Consortium (MTC)”. We also have partnership with many Mainframe 3rd party tool providers.

Key to Macrosoft’s Mainframe-to-Server application conversion capabilities is our depth of experience in both Mainframe, as well as Server [Windows, UNIX] environments, thus insuring a smooth conversion of MVS applications to a Server platform. We have a dedicated center for IBM Mainframe Technologies, and have over a decade of successful engagements in client server technology (.Net, Java, RDBMS, etc.). The Mainframe team consists of the best global talents, and has expertise in most of the mainframe technology areas including JCL, CICS, DB2, VSAM, COBOL,CA-DATACOM, CA-IDEAL, etc.

To the extent possible, we use “Lift & Shift”, which means reusing the existing code on the target platform through standard automated conversions. We have the know-how for such automated conversions to the latest technology such as .Net and MVC architectures. This helps in protecting your earlier investments in programming, debugging and business logic implementation. We also have a standard database migration process (both schema & data) which migrates large volume of data without error from the source database to target database.

Our standardized conversion methodology and procedures insure that the new process will be designed and developed to work efficiently in the new system environment the first time around, and will fully conform to the business rules and processes performed in the original MVS application.

We work directly with the clients to spell out and decide upon all the options for re-constructing a Mainframe application in a Server environment. We establish and maintain a conversion operations handbook that provides a full and complete blueprint and checklist of all steps required, and all processes that need to be performed, whether by us or by the client.

As one example of the types of tradeoffs that we guide the client through, please refer the Vestcom Migration Case Study at wherein we have efficiently and reliably converted more than 230 MVS applications to run on either a Windows platform using an embedded Unix-like environment or directly on a UNIX platform [including Linux].

Our overall objective in all of our work efforts is to confine the conversion process to mostly mechanical execution of automation tools and QA tools, followed in the end by manual side-by-side testing. That is, there should be little or no manual or adhoc coding or programming involved in most conversion efforts.

The methodology we use requires minimum interaction with the client’s mainframe production environment, thereby reducing costs and minimizing interruptions of the production system. This is achieved through a phased activity, in which first a blueprint of the application is generated on a PC, and most of the work is then done at back-office on PCs. Our global delivery model (Offshore-Nearshore-Onsite) further minimizes costs for the client.

2. Migration Process Phases

Viewed from a high level, a complete conversion generally has the following five steps/processes that need to be done in sequential order. Our 5-step MVS conversion methodology involves:

  • Migration Analysis
  • Migration Design
  • Migration Development
  • Migration Installation
  • Migration Monitoring

These are explained below.

2.1 Migration Analysis

This step involves assimilating whatever documentation, specifications, input/output, data formats, naming conventions, business logic, work flow, etc. available from the client, and collecting possible additional information through interactions, questionnaire, etc. This is followed by compilation and analysis of the gathered information. This phase helps in:

  • Forming an overall migration strategy
  • Identifying gaps (Lift&Shift Migrations, Component Development, Tool Partnerships, etc.)
  • Identifying historical, obsolete and unwanted components & data
  • Forming strategy for utilizing the latest technological features of the target environment
  • Identifying additional functional, performance and security requirements of client

This step involves a joint effort of our onshore and offshore team.

2.2 Migration Design

In the context of migration, this step involves the following activities:

  • Detailed Migration Strategy (both Application & Database)
  • MVS Blueprint Generation (detailed below)
  • Target environment selection, assessment & setup (all hardware, software & network)
  • Migration (Development) environment selection, assessment & setup (all hardware, software and team including Development, Test and Preproduction environments )
  • Migration Tools (Lift&Shift) preparation/customization (both application & database migration tools)
  • Substitution/add-on components design
  • PoC / Prototype Migration

The MVS Blueprint Generation involves application analysis for dependencies, and downloading the relevant source code, file structures, etc. to the PC for backoffice processing. This could be a phased process which can extend to the next phase of conversion. The output of this step is the application blue print on the PC in a defined directory structure such as:

JCLsJCLs

ProcsJCL Procedures

CobolCobol source code, copy books, etc

VSAMVSAM file structures

ControlControl Cards

MVS_ChangesChanges during the process of migration

UtilityUtility components

DATACOMDATACOM data structures, definitions, etc.

IDEALIDEAL for DATACOM components

CICSMAPS, Programs

ASMAssembler Programs

DB2DB2 Table Structures, definitions

etc.

Tools that get used in this step include:

  • Macrosoft’s Mainframe Migration Toolkit (especially the JCL,COBOL & DB Analyzer tool )
  • MicroFocus Revolve

This step involves a joint effort of the onshore and offshore teams, and can be done in three modes:

-The onshore team sitting at the client location downloads the files from the mainframe and provides them to the offshore team.

-The offshore team directly accesses the mainframe (from India) through high speed secure VPN connectivity, and downloads the source files directly

-Client downloads the source files and provide them to the offshore team

Which mode to use is decided based on security and other requirements of client.

2.3 Migration Development (Conversion)

This is the major phase of the migration process and in this phase, the following activities take place:

  • Application Conversion & Unit Test
  • Database schema migration
  • Mockup data migration
  • Testing

These activities and processes are further detailed subsequent sections.

2.4 Migration Installation (Live Migration)

In this phase, the live cutover of applications from the source system to target system takes place. The activites involved are:

  • Installation (movement) of converted applications on production system for live run
  • Live Data Migration (This is done in one shot during off hours or holidays.)
  • Live cutover from source system to target system
  • Parallel run

2.5 Migration Monitoring (Post Migration Monitoring)

This phase which could extend from 3 to 6 months, during which period the migrated systems are monitored against the set design targets and any necessary fine tuning is done, including:

  • Trouble shooting & Maintenance
  • Performance Tuning
  • Data Security Audits & fine tuning
  • Backup, Recovery and Disaster Recovery Processes
  • Operations & Administration Processes.

3. Automation and QA Utilities

Macrosoft has built up a number of unique automation tools for performing mainframe conversions that are very useful in reducing the work effort involved in conversions and at the same time significantly reduce the risks and uncertainties of undertaking a conversion effort of this type. Some example modules included among these tools are as follows. (Please refer MMK brochure for all the module descriptions.)

JCL-ANALYZER This simple but powerful tool analyzes JCL to build a web view using HTML/JavaScript. The web view helps programmers understand how JCL works to put applications together by individual job step. This allows programmers who do not have much MVS experience to work on JCL to Shell conversions easily, quickly and efficiently.

JCL Converter: This utility includes both JCL2KORN template and JCL2KORN shell creator. The creator uses templates and JCL step labels to create standard Korn shell for JCL. Within the standard Korn shells, all steps including program calls, utilities, SyncSort and other third party software packages can be handled as separate modules. This utility significantly reduces complexities associated with coding and testing in a teamwork environment.

SHELL Generator: This utility creates execution shells for 3rd party mainframe tools such as SyncSort, that are compliant to the standard system structure set up in the new server environment, which makes migration of 3rd party tools from MVS to PC easy and accurate.

Macrosoft has vast experience in using many industry standard tools for migration and testing. Our partnerships with tool vendors help us in smooth and effective use of these tools. These tools include “Microfocus Revolve” for analysis, and “Microfocus NetExpress” for cross platform COBOL recompiling.

Because of our standard and system independent designs, our MVS-to-Server application conversion technology can be performed under various different work models: On-Site, Off-Site, Off-shore and any mixture of these. Macrosoft works with its clients to review these different work arrangements and assist clients to decide which will work most smoothly and efficiently for their individual circumstances.

4. Critical Elements in the Migration Process

Macrosoft’s approach and capabilities to conversion projects include the following critical elements:

Tools Based Approach: We have extensive experience in converting MVS applications into shell-controlled processes on Windows utilizing an embedded “Unix” environment (e.g. MKS Toolkit, UWIN, CYGWIN, etc.) or directly onto Unix (such as, Solaris, PC Linux). Our Mainframe Migration Toolkit automates the analysis and conversion process as explained above.

Micro Focus Revolve: We have in-depth Micro Focus Revolve Expertise for COBOL and JCL analysis.

Micro Focus Net Express: We have in-depth Micro Focus Net Express Expertise for COBOL re-builds, and data transforms.

IBM Utilities: We have extensive experience and partnerships in successfully converting a large class of IBM Utilities to Windows/Unix (examples include: FileAid, QuickJob, IDCAMS, Syncsort, Transformer, Dialogue, Anchor, etc.). Taping into this depth of experience significantly improves the quality, and speed of our conversion work.

5. Value-of partnering withMacrosoft in Migration

Our Standardized Migration Process: We have standardized the process of migration through a collaborative development environment. The Client participates in every stage of our process. We will share with you our Migration Process Handbook, which we use to direct and manage all conversion activities

Proven & Efficient Project Management Capabilities: The methodologies we use are well proven and efficient, and our Project Management team is well experienced in performing mainframe migrations, having the first-hand experience and know-how to handle most special circumstances and conditions likely to arise in any sizable conversion project.

Proven & Efficient Quality Assurance Processes: Perhaps the most critical success factor in projects of this type involves the methods, technologies and know-how for quality assurance. The methodologies we use are well proven and efficient, and our Quality Assurance teams are well experienced in insuring that converted applications work correctly without significant re-work.

Easily Maintainable & Manageable Code: Client staff is kept fully involved in all phases of the process. There is no ongoing cost or need to involve us further after the conversion work is completed. The client can participate in all project phases, including initial R&D and development, and is educated on the methodologies and tools we use. By the time our work is done, client staff will be fully able to maintain and upgrade the code without our further assistance.

Minimum Extra Investment Required: Our methodology emphasizes utilization of off-shore development resources wherever possible (assuming client approval). Our developers at our Indian facility are able to work remotely accessing the US servers through a secure VPN tunnel connection. This serves three purposes: minimizes overall conversion costs, minimizes resource costs by sharing, and facilitates a collaborative development environment which can generate output throughout the 24-hour daily cycle. We have successfully implemented this methodology.

No special requirements or changes in input data: It is a true one-to-one conversion. The data the mainframe was getting can be taken as is by the Server, and do the processing, and produce exactly what the Mainframe was producing. Hence no special pre-processing or post-processing is required in managing data I/O. The applications are intelligent to handle these issues. The data can be either EBCDIC as in mainframe or ASCII as in PC. These can be managed through configurable parameters.

Batch or interactive processing: Our converted applications provide true batch processing and scheduling as well as restart facility at an intermediate stage in case of failure. The applications can be made batch or interactive, depending on the requirement.

Job Management Console: Our patent software for batched job submission as well as job scheduling provides easy to use user interface to configure, execute and manage the converted applications.

6. Development & Support Processes at Macrosoft

6.1 The Development & Deployment Process

This is managed through collaborative work among the USTeam, the Client Site Team and the Indian Team. 3 dedicated PC servers are used for this purpose, and all the three teams work on these servers remotely. The servers are kept at the client site. There are standard processes for downloading the blueprints (mainframe programs with analysis docs & input data) to the designated directories, uploading the converted modules for unit tests, integration and system test, etc. The final integrated software gets moved to preprod (pre-production) server for trial (parallel) run. On user acceptance, it goes to the production server for the actual run. The authorities and persons to access these functionalities on these servers are well defined (including directory and file name standards), and strictly monitored and controlled.

6.1.1 Coordination of Different teams for collaborative development

The Project Coordinator at US does all the communications and coordination between the teams. Strict document control and flow helps in managing this efficiently.

6.1.2 The India Development Team

The Technical Director coordinates the mainframe migration activity at the India development center. There is Project Manager, Quality Manager & Customer Support Manager under him. Under Project Manager two teams functions, each lead by the respective Project Leader. The Conversion team goes ahead with first level conversions (i.e. Modules). Integration and test of the various modules converted by US & India teams for an application, is the responsibility of the Integration team. Customer Support is a constant activity required by the US teams and Clients. Changes, Part works and debugging support is normally requested by US teams to the Support team. Quality is an independent entity, which controls and assures the quality of the massive works going on.

6.2 The Customer Support Process

The typical customer support process followed at the India development center is depicted below. Client (Overseas team) requests are routed to the support team for the development. On completion it goes to the quality team (QA) for verification, and on QC Pass, it goes to the Sys Admin for upload and delivery. There is a 24-hour support system functioning (due to the difference in working times between US & India). The requests come normally through telephone, chat and email (there are dedicated phone, chat & email ids for this purpose, which are monitored 24 hours a day).