Glossary

An ancestor of a patch is the preexisting software that is being modified or replaced by the patch.

One of four possible states in which a patch is first installed. When a patch is installed, by default it has the patch_state of applied. Other patch states include committed, committed/superseded, and superseded.

The software that will be modified by a patch.

An encapsulation of products, subproducts, and filesets into a single software object. Bundles are a convenient way to group software objects for easy selection. When a bundle is specified in a Software Distributor operation, all products or filesets contained in that bundle are included in the operation. If the filesets within the bundle are patches, this is known as a patch bundle.

An area within a depot that contains all the information needed by SD-UX to define the organization and contents of the products stored in the depot. The catalog (or catalog directory) includes a global index file and a directory of information for each product version in the depot.

The patch state in which the patch is applied and rollback files have been deleted.

The patch state in which the patch is both committed and superseded.

An optional script that is run during software installation, software removal, or software configuration.

A dependency in which a fileset requires that another fileset be installed or configured at the same time. For example, if fileset A requires that fileset B is installed at the same time, fileset B is a corequisite.

Each new patch contains all aspects of all its preceding patches. Patches for HP-UX products are always cumulative.

A relationship between filesets in which one requires another in a specific manner. For example, before fileset A can be installed, it may require fileset B to be installed. SD-UX supports corequisite and prerequisite dependencies.

A fileset that has a dependency on another fileset. For example, if fileset A depends on fileset B, then B is dependent or has a dependency on A.

A repository of software products and a catalog, organized so that SD-UX commands use it as a software source. The contents of a depot reside in a directory structure with a single, common root.

The directory on a target host in which a depot is located. The default is /var/spool/sw.

Patches HP-UX systems, reduces system downtime for software maintenance, provides the ability to install and manage patches on an inactive system image while the system is up and running, allows most software maintenance tasks to be done during normal business hours, limits the downtime required to the time it takes to reboot the system, and enables use of both proactive and reactive patching.

A grouping of one or more files contained in a product or subproduct. A fileset groups a subset of a product's files into a manageable unit. Most Software Distributor operations are performed on filesets.

Is a command-line based tool that consolidates and simplifies patch management and security bulletin management on HP-UX systems. The SWA tool includes Security Patch Check (SPC) and is the HP-recommended utility to use to maintain currency with HP-published security bulletins for HP-UX software. The SWA tool combines the versatility and power of the IT Resource Center Patch Assessment and Security Patch Check (SPC) utilities. SWA has been released for HP-UX 11i systems. SWA can perform a number of checks including published security issues, installed patches with warnings, and missing patches with critical fixes. Once an analysis has been performed, you can use SWA to download any recommended patches or patch bundles and create a depot ready for installation.

An application that facilitates installing and configuring HP-UX systems. Ignite-UX provides a toolset used on HP-UX for doing cold installs and system recovery. It uses SD for doing package-based installs, and can also use golden images for supplying software.

A product that has been installed on a host so that its files can be used by end users. Contrasts with a product residing in a depot on a host's file system. Sometimes referred to as an available product.

Describes the products that are installed on any given host (or within an alternate root). Installed product information is created by the swinstall command, and managed by the swmodify command. The contents of an IPD reside in a directory structure with a single common root.

The pieces of software that SD-UX packages, distributes, installs, and manages. There are three classes of objects: software (installed on target roots or available in depots), containers (depot, roots, alternate roots), and jobs.

Software designed to update specific bundles, products, subproducts, filesets, or files on a system. By definition, patch software is packaged with the is_patch attribute set to true.

Is a collection of patches that have been grouped into a single software object (bundle) to meet a specific need.

Patches have categories, or category tags, associated with them to simplify the process of determining the general purpose of a specific patch.

The process of removing a patch from the system and restoring the system to the prepatched state.

Is a notification that a patch causes or exposes adverse behavior. Patch warnings provide specific information about this incorrect behavior, as well as other important details and recommendations.

A dependency in which one fileset requires another fileset to be installed or configured before the first fileset can be installed or configured. For example, fileset A might require that fileset B is installed before fileset A can be installed. Therefore, fileset B is a prerequisite for fileset A.

The root directory of a product object, in which most of its files are contained. You can change (relocate) the default product directory when you install a locatable product.

HP-UX software management commands. These commands are referred to as SD-UX (Software Distributor-HP-UX).

An SD format structure that contains one or more software products that can be installed on other systems or copied to other depots.

The native toolset used on HP-UX for managing software packages.

The objects packaged, distributed, installed, or managed by SD. A software object can be a file, fileset, bundle, or product. Most operations are performed on filesets.

A subset or partitioning of a software product. A subproduct is an optional component of a product and contains one or more filesets.

The state in which a patch is applied but is then replaced by a superseding patch.

A patch that supersedes all previous patches to a given fileset.

A software depot stored in tape archive (tar) format. Within the archive, directory and file entries are organized using the same structure as any other SD-UX format depot.