Open System Services Porting Guide (G06.29+, H06.06+, J06.03+)

large file aware An application or function that can process large OSS files in addition to small OSS files. For
example, it must be able to access large files as input and generate large files as output. Contrast
with large file safe.
large file safe An application or function that causes no loss of data or corruption of data when it encounters
a large OSS file. A large file safe application or function is not required to process large OSS
files with the same ability as when it processes small files, but it must handle errors or warnings
detected during file manipulation operations and fail gracefully. Contrast with large file aware.
large OSS file A regular file that has a size greater than or equal to approximately 2 gigabytes. Contrast with
small OSS file.
link count The number of directory entries that refer to a particular file.
link name The filename associated with a specific file within a directory. The length of a filename, and
therefore the length of a link name, depends on the file system.
See also filename.
linkfile The object file output of a TNS/R or TNS/E compiler; a linkfile is not executable.
See also loadfile.
loadfile The object file output of a TNS/R native linker (nld or ld) or the TNS/E native linker (eld); a
loadfile is executable but not re-linkable. Loadfiles include programs and DLLs.
See also linkfile.
locale In localization, the definition of the subset of a user’s environment that depends on language and
cultural conventions.
localization The process of adapting computer interfaces, data, and documentation to the culturally accepted
way of presenting information in the culture. Sometimes referred to as “L10N,” derived from the
10 letters between the initial “L” and the final “N” of the word “localization.”
login The activity by which a user establishes a locally authenticated identity on an HP NonStop network
node. Each login has one login name.
login name A user name associated with a session.
LP64 The C/C++ data model where the int data type is 32 bits wide, but long and pointer data
types are 64 bits wide; also used as the C/C++ 64-bit compiler pragma.
See also ILP32.
man page The online or hard-copy version of a file that provides reference information for a software facility.
Some UNIX documentation uses the term “manpage” or “manual page” instead. The online
delivery mechanism used to display the file is usually the shell man command.
See also reference page.
mixed data-model
programming
Programming in an environment in which both 32-bit and 64-bit pointers are used within the
same compilation unit.
mount point A directory that contains a mounted fileset. The mounted fileset can be in a different file system.
mount. To make a fileset accessible to the users of a node.
native mode See TNS/R native mode or TNS/E native mode.
native object code See TNS/R native object code or .TNS/E native object code
native object file See TNS/R native object file or TNS/E native object file.
native object file
tool
See noft utility or enoft utility..
native process See TNS/R native process or TNS/E native process.
native signal See TNS/R native signal or TNS/E native signal.
native-compiled
Itanium
instructions.
See Intel® Itanium® instructions.
native-compiled
RISC instructions
See RISC instructions.
nesting The inclusion of items of one type within items of that type. For example, in the OSS environment,
directories can contain directories.
223