TNS/R Native Application Migration Guide

Introduction to Native Mode

TNS/R Native Application Migration Guide—523745-001

1-10

Data Definition Language (DDL)

The D40 version of the DDL compiler generates host-language source files that can be

used with both TNS and native programs. The DDL compiler inserts pragmas in C and

directives in pTAL and COBOL85 host-language source files to ensure that the same

data alignment is generated, regardless of whether a TNS or native compiler is used.

For details, see Section 7, Data Definition Language (DDL) Migration Tasks.

Native Architecture Features

The native architecture introduces these new features:

•

Native Process Environment

•

Native Object File Format on page 1-13

•

Signals Facility on page 1-13

•

Shared Run-Time Libraries (SRLs) on page 1-14

•

Kernel-Managed Swap Facility (KMSF) on page 1-16

Native Process Environment

A process that runs in TNS mode or accelerated mode—a TNS process—consists

entirely of TNS instructions or both TNS instructions and Accelerator-generated RISC

instructions. A TNS process is initiated by executing a TNS or accelerated program.

A process that runs in native mode—a native process—consists entirely of native-

compiled RISC instructions. A native process is initiated by executing a native

program. Unlike TNS processes, native process do not use or emulate TNS

architecture-specific constructs, such as TNS registers or 16-bit addressing.

The following paragraphs describe differences between native and TNS processes:

•

Process Attributes on page 1-10

•

Process Organization on page 1-11

•

Code Spaces on page 1-11

•

Data Spaces on page 1-12

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.