TNS/E Native Application Conversion Guide

Introduction to Native Mode
TNS/E Native Application Conversion Guide—529659-003
1-13
Native Architecture Features
Native Architecture Features
The native architecture introduces these new features:
•
Native Process Environment
•
Native Object File Format on page 1-16
•
Signals Facility on page 1-17
•
DLLs on page 1-17
•
KMSF on page 1-19
Native Process Environment
A process that runs in TNS interpreted mode or TNS accelerated mode—a TNS
process—consists entirely of TNS instructions or both TNS instructions and Object
Code Accelerator-generated Itanium instructions. A TNS process is initiated by
executing a TNS interpreted or TNS accelerated program.
A process that runs in native mode—a native process—consists entirely of native-
compiled Itanium instructions. A native process is initiated by executing a native
program. Unlike TNS processes, native processes do not use or emulate TNS
architecture-specific constructs, such as TNS registers or 16-bit addressing.
Differences between native and TNS processes are discussed next:
•
Process Attributes on page 1-13
•
Process Organization on page 1-13
•
Code Segments on page 1-14
•
Data Segments on page 1-15
Process Attributes
Native processes have the process attributes HIGHPIN ON, HIGHREQUESTERS ON,
and INSPECT ON by default. For many TNS processes, these process attributes are
set to OFF by default.
Process Organization
Executable code for a TNS/E native process is contained in these objects:
•
The initial program of the process, called user code. This code is read from the
program file.
•
Dynamic-link libraries (DLLs). These include:
°
The system library, which contains system-related procedures and operating
system code that is accessible by the process using system procedure calls.
The system library consists of a set of implicit DLLs.
°
Other DLLs supplied by HP, such as the C run-time library.
°
User-created DLLs.