TNS/R Native Application Migration Guide

COBOL85 Migration Tasks
TNS/R Native Application Migration Guide—523745-001
4-7
Possible Changes Required
•
OPTIMIZE
The NMCOBOL compiler handles OPTIMIZE 2 as if it were OPTIMIZE 1, because
native COBOL does not support global optimization.
OPTIMIZE 0 (no optimization) is recommended the first time you compile a
program with the NMCOBOL compiler. OPTIMIZE 1 (most optimizations) is
recommended for testing and production.
•
RUNNAMED
The RUNNAMED directive works in the NMCOBOL compiler only if you specify the
new RUNNABLE directive (see RUNNABLE directive on page 4-10).
•
SAVEABEND and NOSAVEABEND
The SAVEABEND and NOSAVEABEND directives work in the NMCOBOL
compiler only if you specify the new RUNNABLE directive (see RUNNABLE
directive on page 4-10).
•
SEARCH
For the NMCOBOL compiler, each object-name in a SEARCH directive must
designate a native object file (otherwise the NMCOBOL compiler reports an error).
If a native COBOL85 program references the object in a CALL or ENTER
statement, the object must have been compiled with symbols.
•
SUBTYPE
The SUBTYPE directive works in the NMCOBOL compiler only if you specify the
new RUNNABLE directive (see RUNNABLE directive on page 4-10).
ENTER Statement
The language parameter of the ENTER statement is unnecessary, because the
NMCOBOL compiler can determine the language in which the program is written. If
you do specify language, it must be C or TAL. If you specify TAL, the NMCOBOL
compiler requires a pTAL program (it does not accept TAL programs). If you specify
FORTRAN or Pascal, the NMCOBOL compiler gives an error message. (You must
convert any FORTRAN, Pascal, or TAL programs that your COBOL85 program calls to
native languages, as Step 4 of Migrating COBOL85 Programs on page 4-1 explains.)
Although a native COBOL85 program can use the ENTER statement to invoke C++ or
pTAL programs, language cannot have the value C++ or pTAL.