CRE Programmer's Guide

Glossary
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
Glossary-3
CRE
CRE. See Common Run-Time Environment (CRE)
CREDECS. A file, provided by the TNS CRE, that contains external declarations for
CRELIB functions whose names begin with CRE_.
CRERDECS. A file, provided by the native CRE, that contains external declarations for
CRE function, data, and data structure declarations in pTAL.
DEFINE command. A TACL command that lets you specify a named set of attributes and
values to pass to a process.
eld utility. A utility that collects, links, and modifies code and data blocks from one or more
position-independent code (PIC) object files to produce a target TNS/E native object
file.
See also Binder and nld utility.
emulate. To imitate the instruction set and address spaces of a different hardware system
by means of software. Emulator software is compatible with and runs software built for
the emulated system. For example, a TNS/R or TNS/E system emulates the behavior
of a TNS system when executing interpreted or accelerated TNS object code.
enoft utility. A utility that reads and displays information from TNS/E native object files.
See also noft utility.
execution mode. The (emulated or real) instruction set environment in which object code
runs. A TNS system has only one execution mode: TNS mode using TNS compilers
and 16-bit TNS instructions. A TNS/R system has three execution modes: TNS/R
native mode using MIPS native compilers and MIPS instructions, emulated TNS
execution in TNS interpreted mode, and emulated TNS execution in TNS accelerated
mode. A TNS/E system also has three execution modes: TNS/E native mode using
Itanium native compilers and Itanium instructions, emulated TNS execution in TNS
interpreted mode, and emulated TNS execution in TNS accelerated mode.
extended data segment. A segment that provides up to 127.5 megabytes of indirect data
storage. A process can have more that one extended data segment.
FCB. See file-control block (FCB).
file connector. An abstract entity through which a program accesses a file. It is physically
represented by the file-control block (FCB).
file-control block (FCB). A run-time data object that contains information about an open
file.
file ID. The last of the four parts of a file name; the first three parts are node name (system
name), volume name, and subvolume name.
file name. A fully qualified file ID. A file name contains four parts separated by periods:
•
Node name (system name)
•
Volume name