TNSVU User's Guide

Glossary
TNSVU User’s Guide—528143-003
Glossary-25
TNS compiler
Library (SL). UC and UL exist on a per-process basis. SC and SL exist on a per-node
basis.
TNS compiler. A compiler in the TNS development environment that generates 16-bit TNS
object code following the TNS conventions for memory, stacks, 16-bit registers, and
call linkage. The TNS C compiler is an example of such a compiler. Contrast with
TNS/R native compiler and TNS/E native compiler.
TNS Emulation Library. A public dynamic-link library (DLL) on a TNS/E system containing
the TNS Object Code Interpreter (OCI), millicode routines used only by accelerated
mode, and millicode for switching among interpreted, accelerated, and native
execution modes. See also Shared Millicode Library.
TNS emulation software. The set of tools, libraries, and system services for running TNS
object code on TNS/E systems and TNS/R systems. On a TNS/E system, the TNS
emulation software includes the TNS Object Code Interpreter (OCI), the TNS Object
Code Accelerator (OCA), and various millicode libraries. On a TNS/R system, the TNS
emulation software includes the TNS Object Code Interpreter (OCI), the Accelerator,
and various millicode libraries.
TNS fixup. A task performed at process startup time when executing a TNS object file. This
task involves building the procedure entry point (PEP) table and external entry point
(XEP) table and patching PCAL and XCAL instructions in a TNS object file before
loading the file into memory. See also TNS mode, procedure entry-point (PEP) table,
and external entry-point (XEP) table.
TNS instructions. Stack-oriented, 16-bit machine instructions that are directly executed on
TNS systems by hardware and microcode. TNS instructions can be emulated on
TNS/E and TNS/R systems by using millicode, an interpreter, and either translation or
acceleration. Contrast with MIPS RISC instructions and Intel® Itanium® instructions.
TNS interpreted mode. A TNS emulation environment on a TNS/R or TNS/E system in
which individual TNS instructions in a TNS object file are directly executed by
interpretation rather than permanently translated into MIPS or Intel® Itanium®
instructions. TNS interpreted mode runs slower than TNS accelerated mode. Each
TNS instruction is decoded each time it is executed, and no optimizations between
TNS instructions are possible. TNS interpreted mode is used when a TNS object file
has not been accelerated for that hardware system, and it is also sometimes used for
brief periods within accelerated object files. Accelerated or interpreted TNS object code
cannot be mixed with or called by native mode object code. See also TNS Object Code
Interpreter (OCI). Contrast with TNS accelerated mode, TNS/R native mode, and
TNS/E native mode.
TNS library. A single, optional, TNS-compiled loadfile associated with one or more
application loadfiles. If a user library has its own global or static variables, it is called a
TNS shared run-time library (TNS SRL). Otherwise it is called a User Library (UL).