IBM OS/390 User Manual
•
tailoring and custom modifying the conversion tools through installation
options and exit routines according to the conversion specifications
options and exit routines according to the conversion specifications
•
performing a pilot conversion of a subset of the conversion inventory after
having custom modified the conversion tools
having custom modified the conversion tools
•
auditing the messages and OS/390 material (source code and JCL) produced
by the pilot conversion
by the pilot conversion
•
performing technical tests on a representative sample
The Custom Modification phase is complete when the conversion process
automatically handles the conversion requirements as defined during the
Specifications phase.
automatically handles the conversion requirements as defined during the
Specifications phase.
Two additional items are associated with the objective of Custom Modifications.
They are:
They are:
•
Manually modifying some code for the areas where the tool will not be used
•
Positioning the VSE source to remove incompatibilities
VSE Positioning
VSE Positioning is about modifying the VSE code to eliminate VSE to OS/390
conversion requirements that cannot be automated.
conversion requirements that cannot be automated.
The positioning which doesn
′
t impact the logic of the code, can be applied by
hired consultants. The positioning which impacts the logic of the code
(misplaced stop runs, access to file buffers before open or after close, and so
on), is best left to application support personnel familiar with the code.
(misplaced stop runs, access to file buffers before open or after close, and so
on), is best left to application support personnel familiar with the code.
In any case, the positioned VSE code is then regression tested under VSE by
application support personnel and rolled back into production under VSE. It is
collected later on for conversion, together with the rest of the application
inventory.
application support personnel and rolled back into production under VSE. It is
collected later on for conversion, together with the rest of the application
inventory.
Manual OS/390 Conversion
The objective of manual conversion is to complete the automated conversion
process by applying manual modifications to the OS/390 version of the code,
when fully automating the conversion is too complex or is not cost effective, and
when VSE positioning is also impossible.
process by applying manual modifications to the OS/390 version of the code,
when fully automating the conversion is too complex or is not cost effective, and
when VSE positioning is also impossible.
Manual conversion activities may be required for the conversion of
VSE-dependent Assembler programs, part of the COBOL to COBOL for OS/390
conversion, and a few low occurrence JCL conversion issues.
VSE-dependent Assembler programs, part of the COBOL to COBOL for OS/390
conversion, and a few low occurrence JCL conversion issues.
Manually converted elements are subjected to a one time automatic conversion
to take into account all the conversion requirements that can be automated.
Then they are set apart from the automated conversion process. They are
repetitively supplied with the rest of the application inventory for mass
conversion. Instead of being re-converted each time, they are only source
compared (source compare utility program) to the version manually modified, in
order to identify the latest VSE version changes, if any, and duplicate them
manually in the OS/390 version.
to take into account all the conversion requirements that can be automated.
Then they are set apart from the automated conversion process. They are
repetitively supplied with the rest of the application inventory for mass
conversion. Instead of being re-converted each time, they are only source
compared (source compare utility program) to the version manually modified, in
order to identify the latest VSE version changes, if any, and duplicate them
manually in the OS/390 version.
Because such activity is in contradiction with the mass, automated and repetitive
conversion approach, it is kept to a minimum number of application items that
conversion approach, it is kept to a minimum number of application items that
502
VSE to OS/390 Migration Workbook