IBM OS/390 User Manual
Under VSE/ESA version 1 release 4, and VSE/ESA version 2 and above, the
COBOL compilers available were DOS/VS COBOL, VS COBOL II, and COBOL for
VSE/ESA; CCCA/VSE is available to aid the conversion process. Now, only the
COBOL for VSE/ESA product is available.
COBOL compilers available were DOS/VS COBOL, VS COBOL II, and COBOL for
VSE/ESA; CCCA/VSE is available to aid the conversion process. Now, only the
COBOL for VSE/ESA product is available.
If you are running DOS/VS COBOL, you will have to convert your code to a new
COBOL compiler level. Section 12.3, “Converting from DOS/VS COBOL” on
page 252 outlines the various options open to you, to convert from DOS/VS
COBOL.
COBOL compiler level. Section 12.3, “Converting from DOS/VS COBOL” on
page 252 outlines the various options open to you, to convert from DOS/VS
COBOL.
Section 12.5, “Converting from VS COBOL II” on page 258 outlines some
differences between VS COBOL II and COBOL for OS/390 and VM that you need
to consider when migrating to COBOL for OS/390 and VM.
differences between VS COBOL II and COBOL for OS/390 and VM that you need
to consider when migrating to COBOL for OS/390 and VM.
12.2.1 Migrating Object Code
If you are running VS COBOL II or COBOL for VSE/ESA, it is possible to transfer
your compiled object code from VSE to your OS/390 system, linkedit with OS/390
Language Environment and run it there.
your compiled object code from VSE to your OS/390 system, linkedit with OS/390
Language Environment and run it there.
If you intend to do this, there are two compiler options to consider that affect the
way your program runs under OS/390. These options are DECK and OUTDD.
way your program runs under OS/390. These options are DECK and OUTDD.
DECK
Use the DECK compiler option to produce an object program in a
format that is suitable for migration to OS/390. The object program
produced when the OBJECT compiler option is specified is not
suitable for migration from VSE to OS/390.
format that is suitable for migration to OS/390. The object program
produced when the OBJECT compiler option is specified is not
suitable for migration from VSE to OS/390.
OUTDD
When you run a COBOL for VSE/ESA program under OS/390, the
OUTDD compiler option is used to specify the name of the file for
run-time DISPLAY output.
OUTDD compiler option is used to specify the name of the file for
run-time DISPLAY output.
If you do not specify the OUTDD compiler option, the default is
SYSOUT.
SYSOUT.
You should also check that there are no migration issues that you need to
consider, between Language Environment for VSE/ESA Version 1 Release 4, and
the release of Language Environment running in your OS/390 system. Language
Environment for VSE/ESA 1.4, is functionally equivalent to Language Environment
release 1.4 under OS/390. However, the release of Language Environment
running in your OS/390 system will probably be much higher than 1.4.
consider, between Language Environment for VSE/ESA Version 1 Release 4, and
the release of Language Environment running in your OS/390 system. Language
Environment for VSE/ESA 1.4, is functionally equivalent to Language Environment
release 1.4 under OS/390. However, the release of Language Environment
running in your OS/390 system will probably be much higher than 1.4.
Appendix C of the
COBOL for VSE/ESA Programming Guide has more
information on migrating COBOL for VSE/ESA object programs to OS/390.
12.2.2 Useful Publications
Table 32 on page 252 lists some publications that you may find useful when
planning your conversion. Even if you are planning to convert directly to COBOL
for OS/390 and VM, you may still find the
planning your conversion. Even if you are planning to convert directly to COBOL
for OS/390 and VM, you may still find the
COBOL for VSE/ESA Migration Guide
useful. Also,
Taking Advantage of IBM Language Environment for VSE/ESA has
some useful tips on converting DOS/VS COBOL programs that also apply when
converting to COBOL for OS/390 and VM.
converting to COBOL for OS/390 and VM.
Chapter 12. COBOL
251