IBM OS/390 User Manual
Job Simulation
The goal is to get through as many days as possible. It is a comfort to know at
switchover, that a week
switchover, that a week
′
s jobs can be processed. There are significantly fewer
monthly jobs than weekly jobs. There are significantly fewer yearly jobs than
monthly jobs. Plan the cutover to not occur at month end.
monthly jobs. Plan the cutover to not occur at month end.
The final phase of parallel testing is ensuring the output is the same from both
systems, where actual production is compared to the test output.
systems, where actual production is compared to the test output.
Date Concerns during Parallel Testing
Date concerns at this stage should not be as large a concern because of
synchronizing data for particular day. Be certain that if the output reports run
clean it is not due to them being empty as a result of not finding any date
specific data. Also results can be a bit unpredictable when jobs are run with
dates that are unexpected. Be aware of the age of the dates. If necessary the
dates can be set externally through the JCL.
synchronizing data for particular day. Be certain that if the output reports run
clean it is not due to them being empty as a result of not finding any date
specific data. Also results can be a bit unpredictable when jobs are run with
dates that are unexpected. Be aware of the age of the dates. If necessary the
dates can be set externally through the JCL.
32.6 Implementation Phases
The implementation phases are typically the two weeks that precede the actual
switchover. Once testing indicates that the conversion process is working, your
installation is ready for switchover. After the final mass conversion, switchover
typically requires only a single weekend. The switchover process consists of
backing up the current VSE environment, switching files to OS/390, priming the
MVS catalogs, and initial MVS production operations. This is the period when the
VSE system is frozen. You do not want to be making changes to the VSE system
during these two weeks.
switchover. Once testing indicates that the conversion process is working, your
installation is ready for switchover. After the final mass conversion, switchover
typically requires only a single weekend. The switchover process consists of
backing up the current VSE environment, switching files to OS/390, priming the
MVS catalogs, and initial MVS production operations. This is the period when the
VSE system is frozen. You do not want to be making changes to the VSE system
during these two weeks.
The project phases during the Implementation Phases are:
•
Actual Conversion and Switchover
•
Initial OS/390 Operations
The final and actual mass conversion will be started after MVS tests have been
successfully completed. It will deliver the actual MVS production material. The
actual JCL conversion may be scheduled one or two weeks before the actual
program conversion, in order to apply final manual JCL modifications. There will
also be a special one-time translation of all applications
successfully completed. It will deliver the actual MVS production material. The
actual JCL conversion may be scheduled one or two weeks before the actual
program conversion, in order to apply final manual JCL modifications. There will
also be a special one-time translation of all applications
′
development source
code, but without any compilation or JCL generation.
These phases include the following key tasks:
•
Mass Conversion of Development Source Code
•
Final JCL Mass Conversion
•
Final Program Mass Conversion
•
Initial OS/390 Operations
References for additional conversion information can be found in:
•
Appendix B of the
MVS-MS Planning Guide named
″
Sample Switchover
Plan
″.
Chapter 32. Conversion Process
515