Glossary

[a] [b] [c] [d] [e] [f] [g] [h] [i] [l] [m] [n] [o] [p] [q] [r] [s] [t] [u] [w]

32-bit application

An application compiled using the ILP32 data model.

32-bit API

An Application Programming Interface to the functionality of a 32-bit platform. Includes functions, parameter types, and return types.

32-bit platform

A platform capable of supporting the ILP32 data model.

64-bit application

An application compiled using the LP64 data model.

64-bit API

An Application Programming Interface to the functionality of a 64-bit platform. Includes functions, parameter types, and return types. A 64-bit API is often a superset of a 32-bit API.

64-bit platform

A platform capable of supporting the LP64 data model as well as the ILP32 data model.

a

aC++ compiler

The HP aC++ compiler is based on the ISO/ANSI standard for the C++ language. HP aC++ replaces the HP CC compiler/translator, which is cfront-based.

ABI

Application Binary Interface. The interface by which a compiled application gains access to operating systems and other processor services. An application developed for a specific ABI will run on operating systems that support that ABI.

API

Application Programming Interface. The source-level interface to a set of services provided by a library or system. These services usually take the form of a procedure call, but may also refer to global variables, symbolic constants, and file formats.

application

A set of executables.

application interoperability

In the HP-UX STK, the ability of a 32-bit application to work with a 64-bit application to, for example, exchange data, share objects, and obtain kernel information.

archive library

A library, created by the ar command, that contains one or more object modules. Archive libraries typically have the file name suffix .a. See also: shared library.

b

binary executable

A binary executable is a binary that has been linked and has no unresolved addressing (the linker either used archived libraries, or used shared libraries at execution). Such an executable cannot rely on explicit loading of shared libraries (using the shl_load(3X) or dlopen(3C) function to load a shared library into a running process).

binary file

A file created by the compiler or linker. This file may be a shared library (.sl or versioned), an archived library (.a), a relocatable file (.o), or an executable (see executable).

binary compatibility

A binary executable (a.out, not .o, .a or .sl), that has been compiled in one development environment will operate correctly in a second operating environment. For example, running a binary executable on HP-UX 11.00 that was compiled and linked on HP-UX 10.20. See also: shared library.

breadth-first search order

The dependent library search algorithm used when linking and loading 64-bit applications.

bss segment

A segment of memory in which uninitialized data is stored. See also: hbss segment, text segment and data segment.

c

CC compiler

The HP CC compiler/translator for the C++ language. This compiler has been discontinued, and will no longer be supported after August 1, 2001. Based on the cfront compiler/translator.

certification

The process of testing (usually using a test suite for a standard) to confirm that an executable runs on a later operating system release than it was built on.

cfront

Translator for C++ to C, used as the front end of the HP CC compiler.

COBOL 3.X

HP Micro Focus COBOL Compiler, versions 3.1.35 and 3.2.31. Versions 3.0.50 and 3.0.54 were never released on HP-UX 10.X and therefore are outside the scope of the HP-UX STK.

COBOL 4.X

HP Micro Focus COBOL Compiler, versions 4.0.05 and 4.1.10.

d

data alignment

The manner in which a system or language aligns data structures in memory.

data compatibility

Applications can continue to access persistent data files, such as system files, backup/recovery formats, and HP-documented data formats via supported APIs in the same manner as the previous release.

data model

Description of the sizes of data types, such as int, long, and pointer.

data segment

A segment of memory containing a program's initialized data. See also: bss segment, hbss segment and text segment.

data type promotion

The conversion of operands with different data types to compatible types for comparison and arithmetic operations.

dependency

Occurs when a shared library depends on other libraries -- that is, when the shared library was built (with ld -b...), other libraries were specified on the command line. See also: dependent library.

dependent library

A library that was specified on the command line when building a shared library (with ld -b...). See also: dependency.

depth-first search order

The dependent library search algorithm used when linking and loading 32-bit applications.

destination platform

The new hardware, operating system, and build environment to which you are transitioning your source code.

dynamic loader

Code that attaches a shared library to a program. See also: shared library.

dynamic path searching

The process that allows the location of share libraries to be specified at run time.

e

ELF

Executable Linking Format. The ELF 64 object file format is used for 64-bit object files in HP-UX 11.x. ELF 64 is based on the 32-bit industry standard object file format developed and published by the UNIX Systems Laboratory. The SOM format is used for 32-bit HP-UX 10.x and 11.0. See also: SOM.

EPIC

Explicitly Parallel Instruction Computing. The new "architecture technology" jointly defined by HP and Intel. It is the foundation of the new 64-bit Instruction Set Architecture. EPIC is analogous to CISC and RISC.

executable

A file created by the linker that a computer can execute. Also called a binary.

explicit loading

The process of using the shl_load(3X) or dlopen(3C) function to load a shared library into a running program. Compare with implicit loading.

external reference

A reference to a symbol defined outside an object file.

f

Fortran 77

HP Fortran 77 compiler. This compiler has been discontinued and will become unsupported in summer 2001.

Fortran 90

HP Fortran 90 compiler for HP-UX 10.20 and 11.00. HP Fortran 90 supports the full ANSI X3J3 and ISO WG5 standard, and supports many popular extensions such as Cray pointers and VAX/VMS structures.

g

golden image

A tar, cpio, or pax system archive file containing a known good installation that you install onto other systems using an Ignite-UX server. Golden images can contain the operating system, patches, applications, and customizations.

h

hbss segment

A segment of memory in which uninitialized huge data is stored. See also: bss segment, text segment and data segment.

HP Fortran

HP Fortran compiler for HP-UX. HP Fortran is based on the Fortran95 standards, and supports many popular extensions.

huge data

In general, any data object larger than can be represented on a 32-bit system; more specifically, any data object greater than a specified threshold that is placed in an hbss segment.

i

IA-32

Intel's current architecture for Intel's processors based on their 32-bit instruction set. IA-32 chips include: 486, Pentium ®, and Pentium II ®.

IA-64

The former name for IPF, the next-generation 64-bit architecture that includes the 64-bit Instruction Set Architecture (ISA) jointly developed by HP and Intel. IPF supports 32-bit and 64-bit environments, and provides compatibility with PA and IA-32.

Ignite-UX

The product supplied with HP-UX to do initial configuration and software installation of HP-UX systems. It replaces the HP-UX Cold Install program. Ignite-UX is available free of charge with the HP-UX applications CD-ROM and from the Ignite-UX Web page.

ILP32

The HP-UX 32-bit data model in which int, long, and pointer data types are 32 bits.

implicit loading

Occurs when the dynamic loader automatically loads any required libraries when a program starts execution. Compare with explicit loading.

install

Performing a system transition by rewriting the entire contents of the hard disk(s) with a new operating system using Ignite-UX. It generally involves a system administrator saving selected contents of the disk, using Ignite-UX to initialize the disk with the new operating system, and restoring selected data from the original configuration.

IPF

Itanium Processor Family (IPF) indicates the architecture jointly developed by Intel and HP. Itanium is the first member of Intel's new family of 64-bit IPF microprocessors.

Itanium™

Intel's first microprocessor implementation that uses the 64-bit Instruction Set Architecture (ISA) jointly developed by HP and Intel.

l

LP64

The HP-UX 64-bit data model in which long and pointer data types are 64 bits, and int data types are 32 bits. De facto industry standard for the C language in 64-bit UNIX.

link order

The order in which object files and libraries are specified on the linker command line.

m

magic number

A number that identifies how an executable file should be loaded. Possible values are SHARE_MAGIC, DEMAND_MAGIC, and EXEC_MAGIC.

Merced™

The original development name for Intel's first microprocessor using the 64-bit Instruction Set Architecture (ISA) jointly developed by HP and Intel. The microprocessor is now named Itanium.

n

native

Refers to software that has been compiled for a specific platform.

narrow mode

Refers to a 32-bit application executing on a 64-bit platform.

o

object code

Position independent or relocatable machine code that is generated by compilers and assemblers. Object code does not contain actual addresses; instead, it contains symbols corresponding to actual addresses.

object file

A file containing machine language instructions and data in a form that the linker can use to create an executable program or shared library. See also: shared library.

object module

A file containing machine language code and data in a form that the linker can use to create an executable program or shared library.

p

PA-RISC

HP's Precision RISC Architecture. Also known as HP-PA or PA.

PA-RISC 1.1

HP's Precision Architecture RISC version 1.1. Includes enhancements such as support for both big and little endian and additional floating-point capabilities.

PA-RISC 2.0

HP's Precision Architecture RISC version 2.0. Includes support for 64-bit integer data and 64-bit flat addresses, faster multimedia processing, and additional floating-point changes.

PA8x00

Family of microprocessor chips for 64-bit PA-RISC 2.0.

PA7x00

Family of microprocessor chips for PA-RISC 1.1.

pipe

An input/output channel intended for use between two processes: One process writes into the pipe, while the other reads.

platform

The term used to refer to the hardware, the operating system, and the development environment upon which an application is developed or run.

port

To translate source code to run on a different platform, or the results of performing such a translation. See also: source code transition.

position-independent object code

Object code that contains no absolute addresses. All addresses are specified relative to the program counter or indirectly through the linkage table. Position-independent code can be used to create shared libraries.

pragma

A C directive for controlling the compilation of source.

process

An executable that has been loaded by the kernel (that is, a running executable).

q

qualification

The process of determining whether an existing executable that runs on a previous release of HP-UX will run correctly on a new release of HP-UX. May require minor source code changes and/or recompiling on the previous release. See also: port; source code transition.

r

RISC

Reduced Instruction Set Computing

relocatable file

A file created by the compiler (.o). Archived libraries are also relocatable (.a). They are a collection of one or more relocatable objects. Shared libraries are position-independent code and are not relocatable.

relocatable object code

Machine code that is generated by compilers and assemblers. It is relocatable in the sense that it does not contain actual addresses; instead, it contains symbols corresponding to actual addresses. The linker decides where to place these symbols in virtual memory, and changes the symbols to absolute virtual addresses.

relocation

The process of revising code and data addresses in relocatable object code. This occurs when the linker must combine object files to create an executable program. It also occurs when the dynamic loader loads a shared library into a process's address space.

rollback

The process of resetting a system back to the previous software state. A rollback can include some or all of the operating system, patch, and application software. For example, you can rollback a system from HP-UX 11.0 to HP-UX 10.20 or from patch level 2 to patch level 1. This process requires good backups or an archive created with the Ignite-UX make_recovery tool.

s

scandetail

A source file scanner provided in the HP-UX STK. It helps you perform a source code transition by indicating exactly what API impacts occur on each line of your source files. See Using scandetail and scansummary.

scansummary

A source file scanner provided in the HP-UX STK. It helps you plan your source code transition by determining the number of instances of API impacts in your source files. See Using scandetail and scansummary.

shared executable

An a.out file whose text segment is shareable by multiple processes

shared library

A library created using the ld(1) command that contains one or more position-independent code object modules. Shared library file names end with .sl or a version number. See also: archive library

software transition

There are two types of software transition: source code transition and system transition.

SOM

System Object Model. A 32-bit HP-proprietary object file format for 10.x and 32-bit 11.0 releases of HP-UX. The ELF format is used for 32-bit 11i and 64-bit 11.x HP-UX. See also: ELF.

source code compatibility

A well-behaved, architecture-independent application or library compiled on a previous operating system release can be recompiled without changes on the new operating system release.

source code

A program written in a computer language. Object (machine-language) code is derived from source code during compilation. Source code includes scripts and Makefiles.

source code transition

The process of making software run on a new release of an operating system. This includes qualifying an existing executable on the new operating system, creating a new executable that will run on both the older and the new operating system, or porting source code to the new operating system. The process will vary depending on the state of the executable, the user's objectives, and the compatibility between the old and new operating system releases. See also: port; qualification.

source platform

The hardware, operating system, and build environment on which your original application or library was developed.

standard input/output library

A collection of routines that provide efficient and portable input/output services for most C programs.

STK

The HP-UX Software Transition Kit.

system configuration

The specific files and customizations that create a working environment for a particular user. The system configuration includes but is not limited to:

• Specific operating system version
• Required applications (purchased and locally created)
• User files
• Data files
• Printer information
• Local environment information such as the /etc/hosts file
• Personal user changes to the operating system disk

system swap

The method of building a functional replacement for a given system on a new operating system version, then switching over to using that system. Swapping systems requires redundant system hardware.

system transition

The process of making a server or workstation run using a new release of HP-UX, regardless of the method used or the magnitude of the change. The exact process used depends on the number of systems to be transitioned, the criticality of the change, the redundancy of systems to be transitioned, and the degree of separation between data and system files. The two methods of system transition are installand update.

t

text segment

A segment of read-only memory in which a program's machine language instructions are typically stored. See also: bss segment and data segment.

threads

An independent flow of control within a process, consisting of a context (including register set and a program counter) and a sequence of instructions to execute.

transition

See source code transition and system transition.

u

update

Performing a system transition by in-place replacement of all or parts of the operating system within the existing file system structure on a file-by-file basis. This process does not affect user and application data on the root disk.

upgrade

Performing a system transition using a suite of operating system-specific tools to update your system from an older version of HP-UX to a more recent version of HP-UX. It may also involve determining hardware compatibility.

w

well-behaved

Refers to applications that follow good programming practices for portable programs. These practices include using only documented interfaces, including the required header files, avoiding architecture- specific features, and avoiding APIs that have supportability and compatibility issues. See Coding Practices for Compatibility for details.

wide mode

Refers to a 64-bit application executing on a 64-bit platform.

wrapper

A common frontend program or script for running an executable. For example, a wrapper can check whether the environment is 32-bit or 64-bit and then invoke the appropriate (32-bit or 64-bit) executable.