If for
any reason your shop is unable to
migrate to
Enterprise COBOL and
Language Environment, you can still
take incremental steps to prepare for
migration when these obstacles
no longer apply. For example:
- Evaluate the effort to move to Language Environment.
- Develop a migration plan and long-range schedule.
- Convert your macro-level CICS programs to command-level programs. (For
guidance information, see CICS Application Migration Aid.)
- Code applications based on Enterprise COBOL and Language Environment requirements to
ease a future migration. For example, specify the RES compiler option
instead of the NORES compiler option; all Enterprise COBOL programs
are RES. A "RES-migration" is easier than a "NORES-migration." Link-editing
NORES applications with Language Environment can
result in different behavior, depending on how the programs in the application
are coded. For details, see Link-editing applications with Language Environment.
- Determine which applications contain ILC between C and COBOL.
Verify that the COBOL and C used are supported by Language Environment and
make the appropriate changes as described in the C Migration Guide.
For details, see COBOL and C/370.
- Determine which applications contain ILC between PL/I and VS COBOL II.
Verify that the COBOL and PL/I used are supported by Language Environment,
and link-edit the PL/I programs with the PL/I migration tool. For details,
see COBOL and PL/I.
The PL/I migration
tool allows you to link-edit your PL/I programs gradually, while still running
on the PL/I run time. If you link-edit with the migration tool, you do not
have to link-edit before running under Language Environment.
- Convert all COBOL source code to COBOL 85 Standard.