Filter
Top Products
•
Program clauses that restrict device independence are eliminated; that is,
I/O assignment clauses removed from programs, placed in JCL.
•
Program console interactions (for example, COBOL DISPLAY/ACCEPTs) are
removed from being executed at program runtime; rather this input is
requested at job setup time via job preparation panels and prompts.
The tool converts VSE JCL (procedures, standard label definitions) and the
POWER Job Entry Control Language (JECL) - $$LST, $$PRT, $$PUN, $SLI - into
OS/390 JCL jobstreams. VSE uses of standard utilities are translated into OS/390
equivalents - SORT/MERGE, IDCAMS, and IEBGENER utilities.
The tool lists information in cross reference reports that enables the installation
to make sure that the VSE input libraries are complete. The information
provided includes lists of relationships:
•
Between JCL and PROC/SLI books
•
Between JCL (or PROC/SLI books) and programs, PSB, DBD, or FCB
definitions
•
Between programs and called modules
•
Between programs and copied members or macros
The above data can help the project team determine ″what′s missing,″ ″what′s
duplicated,″ and ″what′s not used″ of the VSE source materials. (It can′t help the
team find missing source, however.) Thus, the tool can assist in one of the most
crucial tasks of the migration; that is, reconciling the ″source VSE materials″
needed for the conversion process. This is sometimes referred to as the Data
Analysis Phase.
In addition to source program and JCL translation, the tool also provides:
•
OS/390 standards naming convention assistance
•
Testing facilities to help when testing converted programs
•
Operator job preparation and submission panels
•
Exits for the tool customizing purposes
•
Operator job logging facilities
•
Online terminal exercises to help in learning the tool operations
3.4 Plan Examples
The following is a sample plan for the migration of ABC Company from VSE to
OS/390. ABC Company will be contracting OS/390 services from SER company.
CNV Company has been contracted to provide professional migration services
and will be using CORTEX-MS.
Chapter 3. Developing the Plan 53