PRINCE Software has specialized in VSE to z/OS (previously VSE to MVS) migrations for over 20 years. We offer extensive experience and a proven track record in the planning and execution of these conversions. Our staff is comprised of data processing professionals, specifically trained and experienced in the disciplines required for a successful migration. This experience, combined with the automation provided by PRINCE Software's MHtran-1 migration software, will assure a smooth, accurate, and cost-effective transition.

The migration of an installation from VSE to z/OS is a major project in terms of cost, time, and the effect on the IT organization. In undertaking such an effort, IT management must ensure that the application conversion is performed properly, in a reasonable time frame, and within the allocated budget. As such, the migration must be a well-planned, organized effort that does not disrupt ongoing activities. Our highly experienced team has performed over 100 such migrations, giving them the capability to handle all the nuances that inevitably occur in a project of this magnitude.

The VSE to z/OS migration process consists of identifying all components of the existing VSE environment, developing alternative actions as to their retention, replacement or conversion, and selecting and implementing the action most appropriate for the proposed z/OS environment.

The use of the MHtran-1 migration software assures the reliability, consistency and productivity that are desired for a project of this scope. We have incorporated into this product the technology needed to translate the VSE applications quickly, accurately and automatically. The product contains:

• Comprehensive inventory tools
• Source code translators for COBOL, BAL, PL/I, RPG II and many 4GLs
• JCL translator
• Specialized migration utilities

• Offer the least risk
• Minimize the impact on ongoing operations
• Enable client personnel to assimilate the skills required to support the newly created z/OS environment
• Assure the greatest opportunity for success

• System Assessment
• Migration Planning
• Application Conversion
• Phased / Mass Implementation

The migration project will be performed using a combination of on-site and remote personnel. During the assessment and planning phases, a senior migration specialist will work on-site with client personnel to develop the migration plans. The conversion of source code and JCL will be performed on the client's z/OS computer resource via a communications link to PRINCE Software's fully staffed migration center in Ramsey, New Jersey. The size and make-up of the migration team will vary during the course of the project to meet the desired schedule and to provide the most cost-effective solution.

• VSE system software and vendor products
• Operations workflow
• Application software inventory
• Program / File dependencies

• Project Organization and Control
• Installation Standards and Procedures
• Revised Operational Procedures
• Application Conversion Workflow

In performing the program and JCL translation, PRINCE Software will not only make those changes absolutely required for z/OS, but will also effect the modifications that are desirable for efficient z/OS performance. A PRINCE Software migration features:

• COBOL for z/OS — PRINCE Software will translate the COBOL programs to conform to IBM's COBOL for z/OS compiler.

• Console Message Handling — console activity will be converted to client specifications. Messages, such as program started/ended, can be removed; special operator instructions may be left on the console; and abnormal condition messages may be moved to SYSOUT. This will allow your personnel to get the information they need to perform their jobs effectively.

• Abnormal Condition Handling — where VSE programs issue an error message followed by a STOP RUN instruction, PRINCE Software technicians will insert instructions to cause the program to abend and the remainder of the job to be canceled without operator intervention.

• CURRENT-DATE Processing — where VSE jobs utilize // DATE statements, PRINCE Software will insert code to assure that the converted program uses the proper date.

• Revised Job-Streaming — If desired, batch job streams may be modified to take advantage of the z/OS increased throughput capabilities. z/OS jobs may be created either as in-stream JCL or catalogued procedures, with restart capabilities built into the appropriate steps.

• I/O Efficiency — Files will be re-blocked to values that make efficient use of I/O and memory resources. Intermediate tape work files may, if desired, be converted to DASD.

The conversion of the application systems will be performed according to the following general procedure:

1. Preparation and Baseline
   • Identify jobstreams constituting a conversion kernel.
   • Transfer source components to the conversion environment.
   • Identify baseline input and output files to be saved and adjust VSE/ESA JCL accordingly.
   • Execute VSE/ESA baseline runs.

2. Translation
   • Translate VSE/ESA programs to z/OS syntax.
   • Make optional changes as defined by migration standards.
   • Generate z/OS JCL.

3. Testing and Verification
   • Run converted z/OS jobstreams and CICS transactions using baseline inputs and creating new outputs.
   • Compare the new z/OS outputs to the VSE/ESA baseline outputs and verify their accuracy.

4. Problem Resolution
   • Research discrepancies and identify causes.
   • Correct converted programs and / or JCL to resolve problems.

5. Acceptance
   • Run parallel tests as required to satisfy acceptance criteria.

The conversion of application systems from one data processing environment to a new one cannot be accomplished in one effort. Systems may be split or combined into manageable groupings called 'kernels'. A kernel's main attribute is its ability to be tested independently of other application systems. This approach provides an experience-proven structure for running a conversion project with tight standards and procedures.

This 'kernelized' approach may also be used for the implementation of the converted systems. The major benefit of this approach is that the amount of work going into production can be highly controlled. This provides a smooth transition period for company personnel to absorb and support the converted z/OS applications.

In situations where the close integration of application systems makes it difficult to implement kernels independently, PRINCE Software will implement its "mass conversion" methodology. Under this scenario, converted and tested systems will be held awaiting completion of all dependent pieces.

Files and databases are pre-positioned to allow for easy fallback and recovery. To ensure program integrity, PRINCE Software will recommend procedures to track and identify changes made to the VSE programs during the period from conversion through implementation. These changes can then be applied to the converted z/OS programs or, if significant, the current VSE version can be reconverted.