IBM OS/390 User Manual
•
Refer to
MVS MS - Production Standards, LB11-8080.
6
Translating the programs, taking into account the differences between VSE
and MVS for each programming language.
and MVS for each programming language.
•
Refer to Part 3, “Converting VSE Languages to OS/390 Languages” on
page 247.
page 247.
•
Refer to the specific program, utility or database section in this book.
•
Refer to 2.7, “Scope of Work and Challenges” on page 32.
7
Converting the job control language. Because VSE and OS/390 differ
significantly in JCL structure and syntax, methods of data distribution and
production methods, JCL conversion is normally the most complex task of
any migration.
significantly in JCL structure and syntax, methods of data distribution and
production methods, JCL conversion is normally the most complex task of
any migration.
•
Refer to Chapter 4, “Job Control Language (JCL) Differences and
Considerations” on page 69.
Considerations” on page 69.
•
Refer to 2.7.3, “JCL Conversion” on page 33.
8
Transferring data files from VSE to MVS.
•
Refer to Chapter 25, “Prepare the Migration Environment” on page 401
for information on system connectivity.
for information on system connectivity.
•
Refer to 32.5, “Conversion Phases” on page 503.
•
Refer 2.7.4, “File Migration” on page 35.
9
Testing converted applications under OS/390.
•
Refer to Chapter 26, “Test Environments” on page 419.
•
Refer to 32.5, “Conversion Phases” on page 503.
•
Refer to Chapter 31, “Diagnosing System Problems” on page 473.
10
Handling the production workload under OS/390, ensuring the jobs are
submitted smoothly while staff is still learning about MVS operations.
submitted smoothly while staff is still learning about MVS operations.
•
Refer to Part 6, “Running Your OS/390 System” on page 435.
•
Refer to 32.6, “Implementation Phases” on page 515.
For a migration process time line that shows the relationship between the
various conversion tasks refer to 3.4.2, “Project Plan Example” on page 56.
various conversion tasks refer to 3.4.2, “Project Plan Example” on page 56.
32.1 Conversion Process Introduction
The following discussions follow the methodology used in the Cortex Migration
System (Cortex MS). Migrations using this methodology are implemented
through a phased project approach. The methodology has proven to be
successful, is well documented, and provides for an orderly discussion of topics.
System (Cortex MS). Migrations using this methodology are implemented
through a phased project approach. The methodology has proven to be
successful, is well documented, and provides for an orderly discussion of topics.
The conversion process of the migration project can be divided into the following
major phases and phase groups:
major phases and phase groups:
1
Preparation Phases
•
Project Management
•
Application Inventory
•
Conversion Specifications
•
Tool Customization
482
VSE to OS/390 Migration Workbook