C/C++ Programmer's Guide (G06.25+)

Glossary

HP C/C++ Programmer’s Guide for NonStop Systems—429301-008

Glossary-7

nld utility

nld utility. The TNS/R native linker for non-PIC TNS/R code. See linker. Compare with the

ld utility, the native linker for PIC (Position-Independent Code).

noft utility. The native object file tool (noft) utility reads and displays information from

TNS/R native object files. See also enoft utility.

NonStop Open System Services (OSS). An application program interface (API) to the HP

NonStop operating system and associated tools and utilities. See Open System

Services (OSS) for a more complete definition.

object code accelerator (OCA). See TNS Object Code Accelerator (OCA).

object code interpreter (OCI). See TNS Object Code Interpreter (OCI).

object file. A file generated by a compiler, Binder, or linker that contains machine

instructions and other information needed to construct the executable code spaces and

initial data for a process. The file may be a complete program that is ready for

immediate execution (a loadfile), or it may be incomplete and require linking with other

object files before execution (a linkfile).

Open System Services (OSS). An open system environment available for interactive or

programmatic use with the HP NonStop operating system. Processes that run in the

OSS environment use the OSS application program interface; interactive users of the

OSS environment use the OSS shell for their command interpreter. Contrast with

Guardian.

OSS. See Open System Services (OSS).

OSS environment. The NonStop Open System Services (OSS) API, tools, and utilities.

pathname. The string of characters that uniquely identifies a file within its file system. A

pathname can be either relative or absolute.

PIC (Position-Independent Code). Executable code that can run at different virtual

addresses.

process. A program that has been submitted to the operating system for execution. An

instance of execution of a program.

process snapshot file. (1) A file containing dump information needed by the system

debugging tool. In UNIX systems, such files are usually called core files or core dump

files.

(2) A file containing the state of a running process at a specific moment, regardless of

whether the process terminated abnormally.