•Part 4, Converting VSE Utilities to OS/390 Utilities
Conversion of the VSE utilities to their equivalent OS/390 utilities is
discussed in this part.
•Part 5, Setting Up the Migration Environment
No two Information Processing environments are alike. Hardware, software,
scheduling, personnel needs will be different in all cases. This part
discusses preparing for and tailoring the test environment, and various
hardware/software combinations and activities that can be performed in
parallel.
•Part 6, Running Your OS/390 System
The OS/390 environment is much different than the VSE environment. This
part provides an orientation to the use of TSO/ISPF, OS/390 console
operation, and OS/390 utilities. Additionally, the systems management
philosophy with OS/390 and diagnosing problems with OS/390 are discussed.
•Part 7, Converting your Applications
This part discusses the application program conversion process and some of
the conversion tools available.
•Part 8, Migration Experience
An example of a migration plan for the ABC company is discussed in this
part.
•Part 9, Appendixes
The appendixes provide useful information including a list of helpful
publications, education information, and a chart mapping Independent
Software Vendor products to OS/390 products.
1.2 Traditional Reasons for Migrating
Users migrating to MVS and OS/390 over the years have done so for a variety of
reasons. While the purpose of this document is to concentrate on the hows of
migrating and not so much the whys, it is interesting to note some of the more
typical or traditional reasons that customers migrate to OS/390.
1.2.1 Business Consolidation
Corporations, more recently, have found themselves involved in business
consolidation activities. Be it for economic and/or efficiency reasons companies
have been faced with the challenge of effectively addressing this type of change.
Consolidating the Information Technology infrastructure is just one of these
challenges. Many have found that combining the system workloads from various
parts of the newly consolidated organization has produced I/T system
requirements beyond the capacity of the VSE operating system. For example,
attempting to combine multiple VSE images into a single system image has often
created situations where multiple processor (n-way) capacity is needed. Prior to
the Turbo Dispatcher (n-way processor support) in VSE/ESA V2, OS/390 (or
MVS/ESA) provided the only solution. Another issue associated with combining
multiple images into a single system image has been the number of VSE
partitions. Similar to the case of the Turbo Dispatcher, prior to dynamic partitions
in VSE/ESA V1, OS/390 (or MVS/ESA) provided a solution to this issue.
4VSE to OS/390 Migration Workbook