IBM OS/390 User Manual
32.6.3.2 Additional Switchover Tasks
These tasks may also need to be addressed during switchover:
•
RJE workstation configurations
•
NJE end users must change their JCL for job submission
•
Configuration of PC workstations
•
Migrate the tape manager to MVS
•
Migrate the database manager to MVS
•
Migrate the Report Manager database to MVS
•
Secure on-site assistance from major vendors
Preparing for switchover takes about a month. A detailed and timed switchover
plan is developed. Final switchover file migration and backup procedures (VSE
and OS/390 JCL streams) are developed, starting from similar procedures used
during testing. The OS/390 environment (catalogs, tape manager, disk space) is
cleaned up from any trace of testing. A final supply of programs and JCL is
compared to the supply used for the final mass conversion. Modified VSE
elements are identified and converted to OS/390 (or the VSE changes are
manually applied to the OS/390 version) to bring the OS/390 applications to
current VSE production level.
plan is developed. Final switchover file migration and backup procedures (VSE
and OS/390 JCL streams) are developed, starting from similar procedures used
during testing. The OS/390 environment (catalogs, tape manager, disk space) is
cleaned up from any trace of testing. A final supply of programs and JCL is
compared to the supply used for the final mass conversion. Modified VSE
elements are identified and converted to OS/390 (or the VSE changes are
manually applied to the OS/390 version) to bring the OS/390 applications to
current VSE production level.
32.6.4 Phase 7: Initial OS/390 Operations
The objective of this task is to support initial OS/390 operations with
conversion-related issues. The conversion team works with the operations team
to analyze and resolve any operations exception created by the conversion of
programs and JCL, or by the file migration. In particular, the conversion team
systematically verifies if the exception is isolated, or if similar cases can be
identified and corrected before they create new operations exceptions. Initial
OS/390 operations typically require 24-hour on-site assistance during the first
week. It tapers down to 12-hour on-site plus 12-hour on call during the second
week, and 8-hour on-site plus 16-hour on call during the third week. The need for
operations assistance by the conversion team ends three to five weeks after
switchover.
conversion-related issues. The conversion team works with the operations team
to analyze and resolve any operations exception created by the conversion of
programs and JCL, or by the file migration. In particular, the conversion team
systematically verifies if the exception is isolated, or if similar cases can be
identified and corrected before they create new operations exceptions. Initial
OS/390 operations typically require 24-hour on-site assistance during the first
week. It tapers down to 12-hour on-site plus 12-hour on call during the second
week, and 8-hour on-site plus 16-hour on call during the third week. The need for
operations assistance by the conversion team ends three to five weeks after
switchover.
After conversion, start your OS/390 system slowly. Ease into it and segment it
where possible. Don
where possible. Don
′
t let the job scheduler run free. Bring up one CICS region at
a time. Run the first batch job and check the results before proceeding. If it is
bad you can still back out. Always allow for a way to return to VSE if you have to.
bad you can still back out. Always allow for a way to return to VSE if you have to.
The assisted MVS operations phase typically lasts three to five weeks. This
phase is complete when all daily, weekly and monthly production jobs have
executed successfully within the MVS environment. This also marks the end of
the VSE to OS/390 migration project.
phase is complete when all daily, weekly and monthly production jobs have
executed successfully within the MVS environment. This also marks the end of
the VSE to OS/390 migration project.
518
VSE to OS/390 Migration Workbook