TNS/R Native Application Migration Guide
TNS/R Native Application Migration Guide—523745-001
1-1
1 Introduction to Native Mode
HP NonStop Series/RISC (TNS/R) native mode enables you to write programs that are
fully optimized for TNS/R systems such as NonStop servers. The term “TNS/R native”
means the program uses the process, memory, and instruction set architectures that
are native to RISC processors.
New native compilers and tools are used to generate native programs. Other tools
have been enhanced to support native programs. Native programs can be written in
the Portable Transaction Application Language, pTAL (a variant of the Transaction
Application Language, TAL), C, C++, and COBOL85. Native programs consist entirely
of RISC instructions and do not have TNS architecture-specific attributes.
To support coexistence and migration, the D4x-series and G-series RVUs have the
same product versions of the native compilers and run-time libraries. This allows you to
use the same source code and object code for nonprivileged programs running on both
HP NonStop K-series systems and HP NonStop S-series systems. For example, you
can compile native C source code on a NonStop S7000 development system and run
the resulting executable object code on a NonStop K20000 production system.
This compatibility assumes that the compilers, run-time libraries, and other
components that your program uses (such as NonStop SQL/MP software) have
corresponding functionality on the specific D4x-series and G-series RVUs you are
using. For example, the D43 and G02 RVUs contain the same native C compiler. If you
install a newer D4x-series RVU, you might need to install a newer G-series RVU to
support new functionality and middleware. (The reverse is also true.) This situation is
similar to having two NonStop K2000 systems (one for development and one for
production), requiring new functionality from a later D4x-series RVU and having to
install the new RVU on both systems.
Subsections:
•
Summary of Execution Modes on page 1-2
•
Native Development Environment on page 1-4
•
Native Architecture Features on page 1-10
•
Benefits of Native Mode on page 1-18
•
Constraints of Native Mode on page 1-19