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

Migration Overview
H-Series Application Migration Guide—429855-006
1-5
TNS Environment
TNS Environment
The H-series RVUs provide the same compilers and tools as the G-series RVUs. Major
differences in the G-series and H-series TNS environments are:
•
A new accelerator tool is provided. The H-series Object Code Accelerator (OCA) is
used instead of Accelerator. (Accelerator is still available on H-series systems for
accelerating TNS object files to be executed on a TNS/R system.)
•
Several new Binder options are provided (see Binder Utility on page B-7 for
details).
•
The H-series OSS environment does not support the TNS development tools.
•
The G-series system-level debugger, Debug, is not supported on H-series
systems. The H-series version of Inspect can be used instead of Debug for
system-level debugging of TNS and SCOBOL processes on H-series systems.
Visual Inspect can also be used for TNS debugging, including the debugging of
TNS snapshot files.
For additional details on the H-series TNS development environment, see Appendix B,
Migrating TNS Applications to H-Series Systems
TNS/E Native Environment
The TNS/E native environment provides tools that enable you to develop programs
that are fully optimized for TNS/E systems. A “TNS/E native” program is a program that
uses the process, memory, and instruction set architecture that are native to Itanium
processors. The TNS/E native environment provides native mode development tools
that have nearly identical functionality to the TNS/R tools. Following are some general
differences:
•
The TNS/E tools have different names (most of the same directives, flags, and
pragmas are supported, and some new ones are added).
•
All libraries are dynamic-link libraries (DLLs). Shared run-time libraries (SRLs) are
not supported. The H-series RVUs provide more comprehensive support for DLLs
than do the G-series.
•
All code is position-independent code (PIC), and all compilers generate PIC. PIC is
used to create DLLs and executable files.
•
Debugging tools have changed. Visual Inspect is still the primary native mode
application debugger, but the H-series product version is enhanced for machine
level debugging. The G-series system-level debugger, Debug, is not supported on
H-series systems. Native Inspect replaces both Debug and Inspect as the system
level and command line debugger for TNS/E native processes. Native Inspect
differs significantly from Inspect.
Note. Native Inspect cannot currently be used to debug COBOL programs. Visual Inspect is the
recommended debugger for H-series COBOL programs.