Binder Manual (G06.27+, H06.04+, J06.03+)

Glossary
Binder Manual—528613-004
Glossary-3
extended data segment
extended data segment. A segment that provides up to 127.5 megabytes of indirect data
storage. A process can have more than one extended data segment.
external entry point (XEP)table. The XEP table contains an entry for each unresolved
external reference and is in the last page of each code segment.
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.
filename. In the OSS environment, a component of a pathname containing any valid
characters other than a slash (/) character or null. In the Guardian environment, the set
of node name, volume name, subvolume name, and file identifier characters that
uniquely identifies a file.
file system. In the OSS environment, a collection of files and file attributes. A file system
provides the namespace for the file serial numbers that uniquely identify its files. See
also ISO/IEC IS 9945-1:1990 (ANSI/IEEE Std. 1003.1-1990), Clause 2.2.2.38.
On an HP system, the Guardian file system for a node is a subset of OSS virtual file
system and is therefore contained within a single fileset. Traditionally, the application
program interface for file access in the Guardian environment is referred to as the
Guardian file system.
Guardian. The original application program interface (API) to the HP NonStop Operating
System.
Guardian services. An application program interface (API) to the HP NonStop Operating
System and associated tools and utilities.
global data. The identifiers that are accessible to all compilation units in a binding session.
high PIN. A process identification number (PIN) that is greater than 255. Contrast with low
PIN.
HP NonStop Operating System. The operating system for HP NonStop systems. The
operating system does not include any application program interfaces.
input control lists. The lists Binder uses to determine which code blocks to include in the
target file.
Inspect region. The region of an object file that contains symbol tables for all blocks
compiled with the SYMBOLS directive or pragma. These tables are used by Inspect.
Also called the symbol region.
Itanium instruction region. Register-oriented 64-bit machine instructions that are directly
executed on TNS/E processors. IPF instructions execute on TNS/E systems, but not
on TNS systems or on TNS/R systems. OCA-generated IPF instructions are produced
by translating a TNS object file using OCA. Native-compiled IPF instructions are
produced by compiling source code with a TNS/E native compiler.