IBM OS/390 User Manual
routines must allow users to custom adapt the tools to specific local conversion
requirements. These requirements, not addressed by standard processing, are
always identified. The conversion tools must be custom modified by positioning
execution options, coding exit routines, and possibly developing some ad-hoc
pre- or post-processors.
requirements. These requirements, not addressed by standard processing, are
always identified. The conversion tools must be custom modified by positioning
execution options, coding exit routines, and possibly developing some ad-hoc
pre- or post-processors.
Finally, tools specifically designed for mass conversion must simplify and
accelerate the review and verification of mass conversion results by producing
summary statistical reports, which allow identifying and assessing at a glance
the conversion of hundreds or thousands of items.
accelerate the review and verification of mass conversion results by producing
summary statistical reports, which allow identifying and assessing at a glance
the conversion of hundreds or thousands of items.
32.2.4 Automated Conversion Process
Assembling and customizing the mass conversion tools result in an automated
conversion process, which converts the entire VSE application portfolio to
OS/390 in only a few hours, including:
conversion process, which converts the entire VSE application portfolio to
OS/390 in only a few hours, including:
•
Collection and verification of the application inventory
•
Translation of application programs and associated macros, copybooks or
subprograms
subprograms
•
Generation of OS/390 load modules
•
Migration of the CICS maps
•
Conversion of other production source items such as FCBs or PSBs and
DBDs
DBDs
•
Conversion of VSE and POWER JCL streams including application and utility
steps and associated SYSIN cards
steps and associated SYSIN cards
•
Generation of new OS/390 JCL complying with the selected OS/390
production standards
production standards
•
Migration of VSE production files to OS/390
32.2.5 CORTEX MS
CORTEX Migration System (CORTEX MS distributed by Sisro Inc.) is the primary
tool for mass conversions from VSE to OS/390. It consists of seven software
components for converting VSE systems to OS/390. All of the CORTEX MS
components are menu-driven through TSO/ISPF panels. CORTEX MS is installed
either on the future OS/390 production system or on a temporary OS/390
conversion system. All seven CORTEX MS components are necessary to
automate the mass conversion. Listed below is a description of the CORTEX MS
software components:
tool for mass conversions from VSE to OS/390. It consists of seven software
components for converting VSE systems to OS/390. All of the CORTEX MS
components are menu-driven through TSO/ISPF panels. CORTEX MS is installed
either on the future OS/390 production system or on a temporary OS/390
conversion system. All seven CORTEX MS components are necessary to
automate the mass conversion. Listed below is a description of the CORTEX MS
software components:
DMT (DOS/OS/390 Translator)
A translator for VSE JCL and programs written in COBOL,
Assembler, PL/1, and RPG II.
Assembler, PL/1, and RPG II.
INT (File Integration)
Consolidates the results of JCL translation, classifies files
according to their life cycle, and loads the Production Database
(PDB).
according to their life cycle, and loads the Production Database
(PDB).
PDB (Production Database)
A batch application change control system that automatically
generates OS/390 JCL to custom defined OS/390 standards.
PDB uses an internal Production Control Language (PCL) for
generates OS/390 JCL to custom defined OS/390 standards.
PDB uses an internal Production Control Language (PCL) for
490
VSE to OS/390 Migration Workbook