Migration Process

Impact and Environmental Analysis Process:
During this process the actual code is examined to establish the complexity of the application. The use of external O/S (Operating System) calls embedded into the application are examined. All JCL is converted to EspBatch equivalent or Shell scripts where necessary.

Strategy and Planning Process:
During this process the detailed project plan is finalized. Finding replacements for the O/S calls (not yet covered with the ESP Products) are investigated. The Test Plan will also be completed during this phase.

Migration and Conversion:

  1. Customization Phase
    The master source code is migrated and resides in the development environment. All necessary customization, development and/or enhancements will take place. The development environment/server will be used for code enhancements, JCL to EspBatch (SCL) and Script conversions, EspMenu/Batch incorporation and new code development where necessary.

  2. ESP Product Incorporation Phase
    EspMenu/Batch are incorporated into all the online programs and menus and functions created from existing profiles. The programs that call JCL/RJE (Online to Batch) modules will be converted to utilize the EspBatch submission method.

Quality Assurance:
The production environment will be configured and a standard Database created containing a mirror image of the development data. This environment will be used for quality assurance on which the migration process will be proved. Only once the system has completed the quality assurance phase will we move into the deployment phase.

Testing:

  1. Functional Testing
    Data from the production environment must be downloaded to simulate a real production environment. Testing at functional level can now begin and Quality Assured. All functions including the uploading - interfaces - to and from other peripheral systems must be tested. The support team must test all aspects of each function and only after the successful signoff will such a function be regarded as tested.

  2. System Testing
    System testing (Parallel Run) can begin as soon as the functional testing has been completed. For this process the production data will be downloaded and an identical process run from the current Mainframe platform executed on the new platform. This parallel process should be done at daily, weekly and monthly level.

    These tests should be based on common weekly and/or monthly functions that can be simulated to provide reasonable assurance that the systems are functionally identical.

  3. Environmental Testing
    The machine and related software will be tested throughout the port to ensure a workable solution. All software versions recommended are already running in production environments elsewhere. Stress tests of the server and network connectivity can also be done during this phase.

Implementation / Deployment:
The production data from the mainframe will be migrated to the production environment. After the successful data verification process has been signed off the Mainframe application server can be decommissioned and all network traffic routed to the new machine.

^ Top
Jump to one of these Chapters.
Click on the name
Executive Summary
Rehosting
Advantages
Pit Falls
Methodology
Migration Process
Product List
References
The following files has been made available to you for downloading.
Right Click > Save As
Cronus Consulting Profile
ZIP FILE | 662KB
ESP Products Overview
ZIP FILE | 485KB
ESP Products Detail
ZIP FILE | 1 726KB
EspSMS Poseidon Help
ZIP FILE | 62KB
SAG EspBatch for Adabas
PDF FILE | 219KB
SAG EspControl for Adabas
PDF FILE | 173KB
Any person using the CRONUS CONSULTING web site for any reason whatsoever, subject themselves to and agree to the following terms and conditions.