Processes

This chapter describes the following processes:

•	Project Definition

•	Asset Generation

•	Asset Cataloging

•	Asset Rationalization (Conditional Step)

•	Target External Specifications

•	Architecture Development

•	Data Conversion

•	Balance Conversion

•	Operations Environment Migration

•	System Integration

•	Maintenance Conversion

•	Production Switch-over

Process List

Project Definition

Purpose

Plan and prepare the work to be performed.

Main Tasks

The main tasks are:

•	Create the hardware and software environments required and prepare the human resources for the project

•	Prepare a workplan including:

•	Detailed planning of the project.

•	Environment and technical requirements.

•	Assignment of resources.

•	Definition of milestones and critical path.

•	Risk mitigation plan.

Asset Generation

This step moves all of the program components, production JCL and the data located in the source production environment to the source test environment.

Purpose

•	Identify and gather the asset information that will be migrated from the source production environment.

•	Freeze and isolate the asset in a source test environment.

•	Prepare this asset information for delivery to the production test environment.

Main Tasks

The main tasks to be conducted are as follow:

•	Identify the component version levels to be migrated.

•	Create and initialize an occurrence of a source test environment.

•	Copy the data and program components into the source test environment.

•	Regenerate all asset executables, including compilations and linkage operations.

•	Based on the analysis of delivered assets, select pilot assets: programs, copies, includes and tables to be included for compilation and linkage.

•	Format the sources onto a suitable media for delivery.

•	Execute and validate the source delivery process from the source test environment to the target environment.

Asset Cataloging

Purpose

•	Define the precise set of components to be converted.

•	Verify the completeness and consistency of the assets.

Main Tasks

The main tasks to be conducted are as follow:

•	Accept the delivered assets.

•	Report on the extracted information.

•	Construct an asset inventory including identification of dependencies outside of the asset set.

•	Verify the completeness and accuracy of the provided source components.

•	Improve the understanding and knowledge of the assets to be migrated, specifically regarding the interdependence between components (transactions, physical files...)

•	Correction of the asset set.

•	Validation of the cataloging results.

•	Choice (or validation of choice) for the pilot set.

Asset Rationalization (Conditional Step)

This process is only necessary when the asset cataloging has found too many errors.

Purpose

•	Constitute an asset set that meets the three quality measurement levels of: completeness, precision and consistency.

Main Tasks

The main tasks to be conducted are as follow:

•	Correction of the asset set (addition, modification, elimination).

•	Cataloging of the new asset source.

•	Measure and qualification of the three quality measurements criteria.

Target External Specifications

Purpose

Provide the following detailed external specifications:

•	The target technical environment.

•	The results of the conversion (schema, screens, language).

Main Tasks

The principal external specification tasks are:

•	Analyze the asset set and the source environment:

•	Pilot Code walk-through.

•	Source performance review.

•	Study the asset set’s technical specifications on the source and target environments.

•	Define the external specifications of each target technical feature: hardware and software configuration, overall technical architecture and architecture implementation.

•	Detailed definition of the asset set’s external interfaces.

•	Specifications of tools and adaptations to the conversion process

•	Definition of the delivery conditions of the converted asset set.

Architecture Development

Purpose

•	To set up and validate the target technical architecture, Oracle database, UNIX OS, Tuxedo and customer specific features.

•	To deliver a prototype configuration that enables to evaluate both a critical batch and transaction process.

•	Measure the response time in regard to performance expectations.

Main Tasks

Provide the following detailed external specifications:

•	Detail the specifications required for:

•	Developments:

•	Related to the source assets to convert.

•	Site specificities.

•	Adapting pre-existing technical components.

•	Define target specifications of the technical components of the TP and batch architectures.

•	Install the target standard architecture.

•	Develop site-specific technical components based upon the requirements detailed above.

•	Integrate and unit test technical components; batch and TP architecture.

•	Integrate and aptitude test asset components.

Data Conversion

Three steps compose the global data conversion process:

•	The data discovery and downloading step.

•	The data remodeling and reloading step.

•	The data static and dynamic validation step.

Purpose

Data Discovery and Downloading

•	Produce the source data unloading programs.

•	Discover, define, clean and unload the source data.

Data Remodeling and Reloading

•	Define, create and validate the Oracle target environments (data base and files).

•	Produce the data conversion tools.

•	Transfer the source data system to the target system.

Data Validation

•	Validate static data to control the migrated data using process execution.

•	Validate dynamic data to control the access control flow to the migrated data using process execution.

Main Tasks

The main tasks include:

Data Discovery and Downloading

•	Identify the data environments of the assets to be migrated.

•	Deliver COBOL data descriptions.

•	Document the data assets.

•	Generation of routines to qualify the data assets.

•	Generation of routines to download the data assets including data transfer to target system.

Data Remodeling and Reloading

•	Study and specify the Oracle target data model.

•	Use Refine for Z/OS Replatforming to generate reloading tools.

•	Use Refine for Z/OS Replatforming to generate target data access routines.

•	Reload target data.

Data Validation

•	Test conversion of drivers in the target environment.

•	Execute programs within both source and target environment.

•	Compare results and identify defects.

•	Correct any defects found.

Pilot Conversion

Purpose

•	Adapt and establish, with Refine for Z/OS Replatforming , the processes that will achieve during the project:

•	A very high accuracy in conversion.

•	A consistently good result.

•	Implement and validate the target technical environment

•	Produce the first conversion subset (when applicable).

•	Validate the performance (load, delivery time and quality) of the implemented process and conversion tools.

Main Tasks

The principal tasks to achieve are:

•	Develop and fine tune the conversion rules that will produce the target components.

•	Setup the target architecture software environment including Oracle database.

•	Convert the whole asset set according to the industrial process.

•	Extract and integrate the pilot onto the target environment.

•	Perform an initial validation of the conversion rules through aptitude tests.

•	Identify possible adjustments regarding project, environment, tools and processes.

Balance Conversion

Purpose

Implement the conversion process for the balance of assets remaining after the pilot conversion using the conversion rules and validated processing used for the pilot set with the same precision and iterative specifications.

Main Tasks

•	Conversion of asset balance using the industrial process validated with the pilot set.

Operations Environment Migration

Purpose

To redefine the production means and procedures for the target environment from the ones that are available in the source environment and in line with the requirements.

Main Tasks

The relevant tasks are divided as follows:

•	Analyze existing components: identify and analyze all components implemented to run in the source system and analyze relevant documentation.

•	Define detailed specifications regarding each target operations component and identify constraints.

•	Produce a detailed definition of each component of the operations sub-set and the choice of tools to use.

•	Set up and configure an approved job scheduler to work with the converted JCL.

•	Adapt the converted JCL to work with the approved job scheduler.

•	Define a detailed execution schedule.

•	Purchase or develop new operations components.

•	KSH development, tools installation, …

•	Develop a production procedures guide in the target environment.

•	Implement and validate each operations component.

System Integration

Purpose

•	Define detailed integration specifications for each integration subset.

•	Define an integration strategy and plan for each integration subset.

•	Define a detailed executions plan.

•	Develop integration tests.

•	Perform integration tests.

Main Tasks

•	Define detailed integration specifications for each integration subset.

•	Define integration strategy and plan for each integration subset.

•	Define detailed executions plan.

•	Test and measure the performance of the migrated applications in the target environment – optimize.

•	Integrate execution tests.

Maintenance Conversion

Purpose

Convert all changes (addition, modifications, and deletions) which occurred between two images of the same asset (total or subset) with the following constraints:

•	Produce a very high quality asset set to minimize the time and workload for validation.

•	Minimize the conversion time to shorten the maintenance freeze period.

Main Tasks

•	Prepare maintenance conversion:

•	Create a Maintenance Guide

•	Plan and prepare maintenance changes

•	Pre-deliver a maintenance image.

•

Catalog.

•	Update converted permanent data:

•	Data discovery, unloading and reloading.

•	Update converted sources:

•	Source conversion.

•	Execute aptitude tests.

•	Execution, comparison and diagnosis.

Production Switch-over

Purpose

Uninterrupted switch over from the source to the target system, complying with the constraints (the size of the switch-over time window specifically).

Main Tasks

The main tasks to achieve are:

•	Define a Switch-over plan describing the global switch-over procedures.

•	Develop a source to target data transfer procedure compatible with the delivery time constraints.

•	Develop a contingency plan.

•	Develop a detailed switch over plan.

•	Validate the detailed plan by a switch-over dry run.

•	Execute final switch over.