TNS/R Native Application Migration Guide

Introduction to Native Mode
TNS/R Native Application Migration Guide523745-001
1-2
Summary of Execution Modes
Summary of Execution Modes
A TNS process—a process that runs in TNS mode or accelerated mode—is initiated by
running a TNS or accelerated object file.
A native process—a process that runs in native mode—is initiated by running a native
object file. Native object files consist entirely of RISC instructions. Native processes do
not maintain TNS architecture-specific constructs.
TNS/R systems support three execution modes:
Because of architectural differences between the execution modes, TNS object code,
accelerated object code, and native object code cannot be mixed in one program file. A
native program can contain only native object code.
Subsections:
Underlying Native Mode Structure for All Programs on page 1-3
Differences Between Accelerated and Native Object Code on page 1-4
Mode Characteristics of Mode
TNS mode
Programs generated by TNS compilers.
Programs use TNS process and memory architecture.
Programs consist of TNS object code.
Programs consist of TNS instructions. Millicode routines implement
TNS instructions on RISC processors.
accelerated
mode
Programs generated by TNS compilers and processed by the
Accelerator.
Programs use TNS process and memory architecture.
Programs consist of TNS object code and accelerated object code.
Programs consist of TNS instructions and equivalent Accelerator-
generated RISC instructions. Programs execute RISC instructions
directly on RISC processors. Programs transition to TNS mode
when Accelerator was unable to generate equivalent RISC
instructions.
native mode
Programs generated by native compilers.
Programs use native process and memory architecture.
Programs consist of native object code.
Programs consist of RISC instructions. Programs execute RISC
instructions directly on RISC processors.