IBM OS/390 Time Clock User Manual


 
References you can consult for additional information about the conversion
specification phases include:
Refer to Appendix C, “DFSMS Naming Conventions” on page 543 for
information on data set naming conventions that relate to an DFSMS
environment.
Refer to Appendix A of the
MVS-MS Planning Guide
for help developing the
Migration Plan.
Refer to Chapter 3 of the
MVS-MS Planning Guide
named Developing the
Conversion Plan″.
Refer to specific product, program or utility migration guides. Examples
include COBOL or DB2 migration guides.
Refer to
MVS-MS Production Standards
document for information on JCL
standards. It does not provide guidance on programs. It does provide a
model of how to structure your jobs, job names, job step names and data set
names.
Recommendations for the specifications phase include taking a training class on
the installation of System Managed Storage (SMS).
The major elements of the Specification phase are:
1. Analyze the VSE source material
2. Design the MVS target output
3. Determine the method to get from source to target
32.4.4.1 Analyze the VSE Source Material
This task is a process of looking at the source material and referring to the
checklist of specification considerations. Your specification document can be
based on the checklist in the
MVS MS Planning Guide - Appendix A
. From this
comparison you can identify the problems or exceptions needing to be resolved
by the conversion team. You may find you are lacking a key utility, or have not
identified a plan to deal with a unique operation or that you have odd JCL.
The analysis of the VSE material is both qualitative and quantitative. Qualitative
analysis consists of listing the types of syntax that are being used in VSE, and
defining the types of replacement syntax that will be used in OS/390. Quantitative
analysis consists of determining the number of times that each type of syntax
occurs within the VSE material.
Quantitative analysis is performed with scan utilities. It is essential in
determining the conversion approach to be used. While conversion issues that
occur numerous times are addressed with automated solutions (if technically
possible), low occurrence conversion issues may be addressed with manual
positioning of the VSE material (when possible) or even manual modification of
the OS/390 version.
The resolution can come during meetings with the services provider and/or site
team where explanations can be presented of why certain things are done the
way they are or why things are where they are.
500 VSE to OS/390 Migration Workbook