Filter
Top Products
and parameters), and library members for control cards. This is because many
of the VSE names are syntactically incorrect under OS/390. But the conversion of
in-house developed applications doesn′t require changing any of the names
associated with the source code. In fact, it is recommended to leave the
program, entry-point, copybook, code include and DD names unchanged to avoid
confusing application support personnel.
The process of developing standards includes striking a balance between the
conventions and familiarity of the VSE system and adopting durable and usable
standards for the future OS/390 system. Follow local conventions wherever
possible. Operators are used to particular names of data sets. Maintaining these
wherever possible will make the transition easier.
32.4.4 Phase 2: Conversion Specifications
The project-specific conversion requirements are determined and documented
during the specifications phase. The specifications phase, which begins with a
″clean″ supply of the conversion inventory (source code and JCL), is typically
completed in two to four months. The specification tasks include:
•
Developing a project plan
•
Educating the conversion project team to the conversion approach and to the
project plan
•
Installing the conversion tools and performing a preliminary tailoring to local
conditions
•
Studying the VSE source production environment
•
Defining the OS/390 target production environment, including OS/390
standards and naming conventions
•
Performing a pilot conversion of a subset of the conversion inventory before
custom modifying the conversion tools
•
Identifying conversion issues and source code positioning activities
•
Designing automated conversion solutions, based on custom modification of
the conversion tools, or development of additional ad-hoc conversion
software
•
Conducting specifications meetings with technical representatives of VSE and
OS/390 operations, technical support, and applications development
The site′s specific conversion requirements are determined and documented by
analyzing the VSE source material, designing OS/390 target material that
complies with the selected OS/390 production standards, and designing the
conversion paths (program translation, JCL conversion, and file migration).
This process comprises knowing what software will be replaced and what
standards will be used in OS/390. It is recommended that DFSMS based naming
standards be used in the design of the MVS target system. These must comply
with the installation′s standards and operations procedures for the MVS target
production.
The Specifications phase is complete when the conversion specifications have
been developed and approved by operations, technical support and applications
development.
Chapter 32. Conversion Process 499