IMS Migration & Modernization

Time-proven IBM^® Information Management System (IMS^TM) applications and database management systems provide valuable business processing that would be expensive to redevelop or duplicate with a custom packaged software solution -- however a shrinking pool of IBM IMS sofware experts is making it increasingly difficult to operate these systems.

Clerity delivers an alternative IBM^® CICS^® environment on cost-effective open systems that makes it possible to rehost IBM IMS business logic and data with minimal risk. Rehosting legacy IBM IMS systems allows proven applications to more fully participate in today's "any time, any place" compute arena and opens access to valuable data across your enterprise.

Datasheet

Clerity follows a set series of steps when migrating IBM IMS workloads. The components of Clerity’s structured process are described below:

		Audit The first step is an audit of the existing mainframe IBM IMS environment. In this stage, all source components are loaded into the migration toolset and an application repository (or inventory) is established. Source code and data files, including items such as Database Descriptions (DBDs), programs, Job Control Language (JCL), and Maps, are checked for completeness and complexity.
		Model After an application repository has been established, programs and data files are analyzed to build a data repository of rules to be used during the conversion. Message Format Service (MFS) screens are also analyzed so that Basic Mapping Services (BMS) screen models can be built.
		Generate During this phase, the relational database model is created, along with Data Definition Language (DDL) and load scripts. Application programs are updated to reflect new Relational Database Management System (RDBMS) query structures and required IBM CICS transaction code, and interface routines are also generated.
		Build During the build stage, the new RDBMS database is populated with the original IMS data and all source programs and maps are compiled to construct the new, target executable system.
		Test Thorough unit and system testing needs to be performed to ensure successful production cutover. If discrepancies are discovered during this stage, relevant inputs and required adjustments are made. The process can then be rerun until all functional and service level requirements are met.

The final stage is deployment of the new system. Once system testing is complete, the environment is ready to be released into production.

Read more about IBM IMS application rehosting solutions from Clerity.