Many OS/VS COBOL CICS programs
must be changed in order to compile them with Enterprise COBOL.
The CCCA tool can make all of these changes automatically, or you can make
the changes yourself using the information in this section. For more information
on CCCA, see Conversion tools for source programs.
The following considerations apply when you migrate
COBOL applications
to use the integrated CICS translator:
- Delete the separate translation step from the compile process.
- Change the XOPTS translator option to the CICS
compiler option. The suboptions string must be delimited with quotes or apostrophes.
For example, a program to be translated by the separate CICS translator might
have a CBL statement like this:
CBL TEST(NONE,SYM), XOPTS(LINKAGE,SEQ,SP)
For
the integrated CICS translator it must be changed to this:
CBL TEST(NONE,SYM), CICS('LINKAGE,SEQ,SP')
- Do not use SIZE(MAX)
when you compile programs that contain CICS statements. Storage must be left
in the user region for the translator services.
- Move all CBL/PROCESS
statements to the first lines of the source program. The integrated CICS translator
does not accept comment lines preceding a CBL/PROCESS statement. The source
program must conform to Enterprise COBOL rules.
- Check if you have nested programs that
redefine DFHCOMMAREA. The integrated translator will not generate declarations
of DFHCOMMAREA or DFHEIBLK in nested programs. DFHCOMMAREA and DFHEIBLK declarations
are generated in the outermost program with the GLOBAL attribute specified. COBOL programs that
depend on these generated declarations within nested programs require source
changes.