H-Series Application Migration Guide (H06.03+)

Native COBOL Migration Tasks:
H-Series Application Migration Guide—429855-006
6-5
TNS/E COBOL Uses IEEE Floating-Point Format
TNS/E COBOL Uses IEEE Floating-Point
Format
Both TNS/R native and TNS/E native COBOL use floating-point data values for certain
internal calculations. TNS/R native COBOL uses the HP proprietary TNS floating-point
format, whereas TNS/E native COBOL uses the IEEE format (no option is provided to
use TNS floating-point). This use of IEEE floating-point format might provide a slight
performance advantage over the TNS format; however, the results of floating-point
calculations might differ slightly.
Alignment of Level-01 and Level-77 Data Items
Changed
The alignment of level-01 and level-77 data items is different in TNS/E native COBOL.
This difference can affect TNS/R and TNS/E programs that share data.
In TNS/R native COBOL, level-01 and level-77 data items are aligned on a 2-byte
boundary. In TNS/E native COBOL, these items are aligned on an 8-byte boundary.
For consistency with TNS/R COBOL, you can direct the TNS/E native COBOL
compiler to align level-01 and level-77 data items on a 2-byte boundary by adding the
SYNCHRONIZED clause to their declarations.
Alignment of all other data items is the same for TNS/R native COBOL and TNS/E
native COBOL, allowing COBOL programs in both environments to freely share data
files.
Files Renamed
Native COBOL files are renamed in H-series RVUs. Any occurrence of the TNS/R
native name must be replaced with the corresponding TNS/E native name:
References to the preceding files might appear in these contexts:
•
CONSULT directive
•
LIBRARY directive
•
SEARCH directive
•
File-mnemonic clause of the SPECIAL-NAMES paragraph
•
OF or IN clause of the CALL or ENTER statement
TNS/R Name TNS/E Name
NMCOBEX0 ECOBEX0
NMCOBEX1 EXOBEX1
NMCOBEXT ECOBEXT