TNS/E Native Application Conversion Guide

Converting COBOL Programs
TNS/E Native Application Conversion Guide—529659-003
4-2
Converting COBOL Programs
•
The data space limit of approximately 60 KB for the sum of all the Working-Storage
Sections and File Sections of a TNS process does not apply to native COBOL
programs. The Working-Storage Section and the Extended-Storage Section are
the same in native COBOL.
•
In TNS/E native COBOL, there is no distinction between the small data area and
the large data area.
Converting COBOL Programs
The recommended procedure for conversion from TNS COBOL to native COBOL is:
1. Change your program so that it runs in the Common Run-Time Environment
(CRE), if it does not already. (See the COBOL Manual for TNS/E Programs .)
2. Verify that you have adequate system resources for the converted programs.
Native object files use approximately the same amount of disk space as
accelerated object files. Native processes use approximately the same amount of
processor memory as TNS processes running in accelerated mode.
3. If necessary, change your source program (see Changing the Source Program on
page 4-4).
To learn whether you must change your source program, compile it with the native
COBOL compiler, which issues warnings when it encounters source constructs that
it does not accept. Running the native COBOL compiler with the DIAGNOSE-85
directive is especially recommended. This directive causes the native COBOL
compiler to issue warnings when it encounters source constructs that could cause
the program to produce different results than it would if it were compiled with the
TNS COBOL compiler. For a complete description of the DIAGNOSE-85 directive,
see the COBOL Manual for TNS/E Programs .
4. If your program calls TNS programs, convert them to native mode. Native
programs cannot call TNS programs. For the following list of languages, follow
these instructions. The last one, Data Alignment on page 4-3, applies to several
languages.
•
C/C++
Recompile C and C++ programs with the native C and C++ compilers,
respectively. Specify the SYMBOLS pragma when recompiling a C or C++
program that your TNS COBOL program references in a CALL or ENTER
statement. This generates symbols for use by a symbolic debugger.
•
TAL
Convert TAL programs to pTAL. (See the pTAL Conversion Guide .) Some CRE
library routines might no longer exist, so you might have to change calls to
them. Also, if you want to reference an object in a CALL or ENTER statement,
you must compile your pTAL program with symbols.