TNS/E Native Application Conversion Guide

Developing a Conversion Strategy
TNS/E Native Application Conversion Guide—529659-003
2-3
Maintaining Common Source Code for TNS and
TNS/E Native Compilers
Maintaining Common Source Code for TNS
and TNS/E Native Compilers
If your program requires few changes to convert to native mode, you can often
maintain common source code for the TNS and native compilers. If your program
requires extensive or complex changes to convert to native mode, maintaining
common source code is impractical.
By using D3x or later versions of the TNS compilers and H-series versions of the
native compilers, you can maintain common source code for the D3x and H-series
operating system RVUs. (Because of differences between the D20 and D30 TNS
compilers, it is too difficult to maintain a common source between the D20 and
H-series operating system RVUs.)
To maintain a common source, use features available in the D3x or later RVUs and
features available to TNS and TNS/E native programs. Features that you cannot use
include:
•
C++ language features that the cfront C++ preprocessor cannot process
•
pTAL language features that the TAL compiler does not support
•
The small-memory model in C and the 16-bit data model in C and C++
•
COBOL language features that are not supported by both the TNS COBOL and
native COBOL compilers
To maintain a common source, you must use:
•
Separate build scripts to run the TNS and native compilers and other tools
•
D3x versions of the TNS C compiler
•
D32 or later versions of the TNS COBOL compiler
•
D31 or later versions of the TAL compiler
•
Versions of the Guardian procedure external declaration files (EXTDECS and
CEXTDECS) and the C header files that correspond to the RVU
•
COBOL dummy files (COBOLEX0, COBOLEX1, COBOLEXT, ECOBEX0,
ECOBEX1, and ECOBEXT)