TNS/E Native Application Conversion Guide

Converting COBOL Programs
TNS/E Native Application Conversion Guide—529659-003
4-6
Possible Changes Required
Possible Changes Required
The TNS and native COBOL compilers handle the following directives, the ENTER
statement, floating-point arithmetic, and checkpointing differently. Make any necessary
changes to them before compiling your COBOL source program with the native
COBOL compiler. For complete descriptions of the directives, see the COBOL Manual
for TNS/E Programs .
•
Directives on page 4-6
•
ENTER Statement on page 4-7
•
Floating-Point Arithmetic on page 4-7
Directives
•
BLANK and NOBLANK
For the TNS COBOL compiler, BLANK is the default. For the native COBOL
compiler, NOBLANK is the default.
•
CONSULT
For the native COBOL compiler, each object-name in a CONSULT directive
must designate a native object file (otherwise the native COBOL compiler reports
an error). If a native COBOL program references the object in a CALL or ENTER
statement, the object must have been compiled with symbols.
•
LARGEDATA
For the TNS COBOL compiler, the LARGEDATA directive determines whether
individual data items are located in the user data space or the user extended
space. The default value for the LARGEDATA directive’s parameter is 256.
The native COBOL compiler does not distinguish between user space and
extended space. The LARGEDATA directive is ignored, and a warning is reported.
•
LIBRARY
The native COBOL compiler issues a warning for the LIBRARY directive.
In native COBOL, a user library is implemented as a dynamic-link library (DLL).
Instead of the LIBRARY directive, specify the name of your DLL as explained in
the COBOL Manual for TNS/E Programs .
•
RUNNAMED
The RUNNAMED directive works in the native COBOL compiler only if you specify
the new RUNNABLE directive (see RUNNABLE directive on page 4-11).
•
SAVEABEND and NOSAVEABEND
The SAVEABEND and NOSAVEABEND directives work in the native COBOL only
if you specify the new RUNNABLE directive (see RUNNABLE directive on
page 4-11).