Glossary

A structure attached to a software object that defines access permissions for multiple users and groups. It extends the permissions defined by the HP-UX file system's mode bits by letting you specify the access rights of many individuals and groups instead of just one of each.

See local host.

The agent (swagent) runs on the local host. It services all selection, analysis, execution and status requests. It is scheduled by the daemon and guided by the SD-UX controller.

A depot directory located someplace other than the default location.

A Target for software installation, where the Target is not the primary Root (/) and where the software can be stored or referenced, but not configured or used.

The second phase of a software installation, copy, or remove operation, during which the host executes a series of checks to determine if the selected products can be installed, copied, removed, or verified on the host. The checks include the execution of check scripts and disk space analysis (DSA).

An attribute that names a previous version of a fileset. This is used to match filesets on a target system. If the match_target option is set to true, SD-UX matches the ancestor fileset name to the new fileset name.

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

A keyword that represents the operating system platform on which the product runs.

A .o file that needs to be replaced in an existing archive using the ar command. Used for patch files.

An operation in which SD-UX runs an interactive request script to get a response from the user. Request scripts can be run by the swask, swconfig, and swinstall commands.

Information describing a software object's characteristics. For example, product attributes include revision number, tag (name), and contents (list of filesets). Fileset attributes include tag, revision, kernel, and reboot. File attributes include mode, owner, and group. An essential part of the Product Specification File, attributes include such information as the product's short name or tag, a one-line full name title or a one paragraph description of the object. Other attributes include a multi-paragraph README file, a copyright information statement and others.

In SD-UX security, checking that a user has the necessary permissions to perform a specific action, as defined by an Access Control List.

Software that will be modified by a patch.

Packaging the source files and information into a product, and creating/merging the product into the destination depot/media.

A collection of filesets that are encapsulated for a specific purpose. By specifying a bundle, all products or filesets under that bundle are automatically included in the operation.

A file that contains the name and attributes of targets selected by swinstall or swcopy.

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. It includes a global INDEX file and a directory of information for each product version in the depot. It is sometimes referred to as the catalog directory.

This keyword defines the "category" attribute for the product object. It refers to the type of software being packaged.

Compact Disc-Read Only Memory or a SD-UX depot that resides on a CD-ROM.

See remote operations.

An optional, script associated with a product or fileset, executed by swinstall during the analysis phase. The result returned by the script determines if the fileset can be installed or updated.

An optional script associated with a fileset that is executed during the swremove analysis phase. The result returned by the script determines if the fileset can be removed.

Cyclic Redundancy Check (CRC), a computed value that is compared with stored data to tell if a file has been corrupted during transfer.

Command Line Interface. See Command Line User Interface.

Usually refers to diskless server computer. Previous versions of SD-UX supported diskless clients.

See Command Line User Interface. All SD-UX commands can be run from the command line. See also GUI, TUI, and IUI.

Optional parameters for a command entered with the command itself at the HP-UX command line prompt. See also default options.

Text-formatted commands and options entered at an HP-UX command line prompt or executed by a script. SD-UX also has a Graphical User Interface (GUI) and a Terminal User Interface (TUI) for the sd, swinstall, swcopy, swlist, and swremove commands.

The state in which a patch is applied and rollback files have been deleted. Other patch states include applied and superseded and committed/superseded.

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

The ability of swinstall to filter the software available from a source according to the host's uname attributes. Software products are created to run on specific computer hardware and operating systems. Many versions of the same products may exist, each of which runs on a different combination of computer hardware and operating system. By default, swinstall does not allow selection and installation of incompatible software.

A software product that will operate on a given hardware system. Software that passes compatibility filtering for a local host. Also see Incompatible Software.

An optional script associated with a fileset and automatically executed by swinstall (or manually executed by swconfig) after the installation of filesets is complete.

A special ACL (global_soc_template) that is used to create initial ACLs for depot and roots. See also product ACL template.

A keyword used to assign filesets to subproducts. This allows a fileset to be contained in multiple subproducts.

Optional scripts packaged with software or added to software by modifying the IPD. Control scripts are run during swconfig, swinstall, swremove, or swverify operations. Control scripts may include: configure or unconfigure for swconfig; checkinstall, preinstall, postinstall and configure scripts for swinstall; the checkremove, unconfigure, preremove, and postremove scripts for swremove; and the fix or verify script for swverify.

The SD-UX programs or commands (swinstall, swcopy, etc.) that are invoked by the user on the local host and that direct the actions of an SD-UX agent.

A keyword that defines the copyright attribute for the destination depot (media) being created/modified by swpackage. It refers to the copyright information for the software product.

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.

A fileset containing software critical to the correct operation of the host. Critical filesets are those with the reboot and/or kernel fileset flags. During swinstall's load phase, critical filesets are loaded and customized before other filesets.

See superseding patch.

The SD-UX program that schedules the agent to perform software management tasks. On a SD-UX controller, the daemon polls the job queue for scheduled jobs.

The internal attribute for SD-UX INDEX file syntax. Layout_version 1.0 uses data_model_revision 2.40; whereas, layout_version 0.8 uses data_model_revision 2.10.

Distributed Computing Environment. Technology used by SD-UX for distributed communications. Controllers, daemons, and agents communicate using the DCE Remote Procedure Call (RPC).

The file (either
/var/adm/sw/defaults.hosts for system level defaults) or
/$HOME/.sw/defaults.hosts for user level defaults) that contains the default list of hosts for SD-UX commands.

Changeable values that affect SD-UX command behaviors and policies. Default options are contained in the defaults file. See Appendix A “Command Options” for more information.

The file (either
/var/adm/sw/defaults for system-wide defaults or
$HOME/.sw/defaults for user- level defaults), which contains the default options and operands for each SD-UX command.

SD-UX provides a controlled access to depot-resident products: both the host where the agent is running and the user initiating the call (delegation) must have read access.

A relationship between fileset 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, exrequisite, and prerequisite dependencies. See Dependent.

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

A repository of software products and a catalog, organized so SD-UX commands can use it as a software source. The contents of a depot reside in a directory structure with a single, common root. A depot can exist as a directory tree on a SD-UX file system or on CD-ROM media, and it can exist as a tar archive on a serial media (tape). All depots share a single logical format, independent of the type of media on which the depot resides. Depots can reside on a local or remote system. You can package software directly into a depot or copy packaged software into the depot from elsewhere.

See depot.

An attribute for products and filesets, usually a paragraph description of that product or fileset.

The path at which a file will be installed.

In the GUI or TUI, a dialog box that lets you get more information about a specific process to monitor its progress.

A system where software application files are placed for further integration and preparation for distribution. You may use a developer host to assemble, organize, and create product tapes or depots.

In packaging, a keyword that defines the a directory for a product object. The directory specified is a default, absolute pathname to the directory in which the product will be installed.

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

A process that determines if a host's available disk space is sufficient for the selected products to be installed.

Overwriting an installed version of software with an older version.

See Disk Space Analysis

An optional keyword that ends the software object specification in a PSF. No value is required.

A dependency in which a fileset requires the absence of another fileset before it can be installed or configured. For example, if fileset A cannot be installed or configured if fileset B is already installed, fileset B is an exrequisite for fileset A.

A collection of files. Most SD-UX operations are performed on filesets.

An OSF/Motif ™ user interface, with windows and pull-down menus, provided with the sd, swinstall, swcopy, swlist, and swremove commands. See also the Command Line User Interface (CLUI) and Terminal User Interface (TUI).

In SD-UX security, a set of users.

In SD-UX security, the user's primary group.

See Graphical User Interface.

A variable that contains the path of the current user's local log-in directory.

A computer system upon which SD-UX operations are performed. See local host and controller.

The ACL that is attached to and controls access to the host object.

Software products are created to run on specific computer hardware and operating systems. Many versions of the same products may exist, each of which runs on a different combination of hardware and operating system. Incompatible software does not operate on the host(s) because of the host's computer hardware or operating system. The default condition in swinstall is to disallow selection and installation of incompatible software.

In packaging, an INDEX file defines attribute and organizational information about an object (for example, depot, product, or fileset). INDEX files exist in the depot catalog and the Installed Products Database to describe their contents.

An INFO file provides information about the files contained within a fileset. This information includes type, mode, ownership, checksum, size, and pathname attributes. INFO files exist in the depot catalog and the Installed Products Database to describe the files contained in each existing fileset.

Defaults files, option files, software selection files, target host files, and session files that modify and control the behavior of the SD-UX commands.

A command that lets you install the SD-UX product from media or a depot onto a workstation or server. You may need to install SD-UX if the version on your system is corrupted or deleted. This command, along with update-ux, replaces the older swgettools command.

A product that has been installed on a host so that its files can be used by end-users, as opposed to 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 swinstall, and managed by swmodify. The contents of an IPD reside in a directory structure with a single common root.

A product attribute in the Installed Products Database (IPD) that lets you uniquely identify products with the same tag (name) or revision.

In packaging, a keyword that defines whether a product can be installed to an alternate product directory or not. If specified, the attribute is set to a value of true. If not specified, the attribute is assigned a value of false.

Interactive User Interface, a generic term that can mean either the Graphical User Interface (GUI) or the Terminal User Interface (TUI).

A SD-UX task created by the swinstall, swcopy, swremove, swverify, or swconfig commands. You create, monitor, schedule, and delete jobs using the Job Browser. You can also monitor jobs using the swjob command.

A GUI program that lets you create, monitor, schedule, and delete jobs. The GUI is activated by the sd command. You can also monitor jobs using the swjob command.

Unique numbers generated by SD-UX to identify jobs.

A fileset that contains files used to generate the operating system kernel. During the swinstall load phase, kernel filesets are loaded and customized before other filesets.

In packaging, a word (or statement) that tells swpackage about the structure or content of the software objects being packaged by the user. Packaging information is input to swpackage using a Product Specification File.

The third phase of a software installation or copy operation; when swinstall and swcopy load product files on to the host; and when swinstall performs product-specific customization.

The host on which SD-UX commands are being executed. Sometimes called the administrative host. The local host executes the controller, which may direct operations on multiple remote systems when remote operations are enabled.

A product that can be relocated to an alternate product directory when it is installed. If a product is not locatable, then it must always be installed within the defined product directory.

Each SD-UX command records its actions in log files (the swlist command is an exception). The default location for the various log files is
/var/adm/sw/<command>.log

In packaging, a keyword that type of systems on which the product will run. (If not specified, the keyword is assigned a wildcard value of * (meaning it will run on all machines.) If there are multiple machine platforms, you must separate each machine designation with a | (vertical bar).

In packaging software to a distribution tape, this phase actually copies the contents of the temporary depot to the tape.

Physical data storage media on which software is stored, such as tape, CD-ROM, or DVD.

Minimum Free Threshold, the minimum amount of free disk space required to store products being packaged.

A single product that contains different versions of the same fileset.

There can be multiple network sources from a single host, each one a different depot served by that host's single swagentd daemon. A network source is identified by the host name and depot directory.

Another name for client host. See Client.

In packaging, a keyword that defines the part or manufacturing number of the distribution media (CD or tape depot).

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.

Operating System.

An attribute indicating the owner of the file (string).

Installable SD-UX format software created with swpackage. Packaged software can be placed in a depot for distribution.

A phase where swpackage builds source files and information into a product object, and inserts the product into an existing depot. If the depot does not exist, swpackage creates a new depot but does not register it.

In packaging, reading the product_specification_file to determine the product, subproduct and fileset structure; the files contained in each fileset; and the attributes associated with these objects.

The swpackage program, which packages software for later distribution to Target systems.

The task of creating a package.

Software designed to update specific bundles, products, subproducts, filesets, or files on your system. There are point patches and superseding (cumulative) patches. By definition, patch software is packaged with the is_patch attribute set to true.

An attribute that specifies the full pathname for a file.

Patches that patch separate parts of the same base fileset.

POSIX 1387.2-1995 IEEE standard, on which SD-UX is based.

An optional, script associated with a fileset that is executed by swinstall after the corresponding fileset has been installed or updated.

An optional, script associated with a fileset that is executed by swremove after the corresponding fileset has been removed.

An optional, script associated with a fileset that is executed by swinstall before installing or updating the fileset.

An optional, script associated with a fileset that is executed by swremove before removing the fileset.

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 may require that fileset B is installed before fileset A can be installed. Therefore, fileset B is a prerequisite for fileset A. See dependency, corequisite, and exrequisite.

A system on which software is installed and configured.

In SD-UX security, the user (or host system, for agents making RPCs) that originates a call to another system.

A collection of subproducts and/or filesets.

In SD-UX security, the ACL used to initialize the ACLs that protect new products on depots that are created by the host.

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 installing a locatable product.

An input file that defines the structure and attributes of the files to be packaged by swpackage.

A depot can contain multiple versions of a product. Product versions have the same tag attribute, but different version attributes. See Multiple Version. The installed products database supports multiple installed versions of a product. Installed versions have the same tag attribute, but different version attributes or a different product directory.

Software that you cannot install or copy unless you provide a codeword and customer ID. (These are found on your software certificate in your media kit.) You can use codeword-protected software only on systems that for which you have a valid license to use that software.

Getting software products from a depot to be installed or copied onto the local system. See also push.

Performing software management (usually installing or copying) on multiple remote target systems from a central controller. See remote operations.

This keyword defines the "readme" attribute for the product object. A text file of the README information for the product; either the text value itself or a file name that contains the text.

In SD-UX security, the scope of the authority by which the principal is authenticated.

A process that determines what depots are available on a given host and makes them available for use. Registration information consists of the depot or root's identifier (its path in the host file system). This information is maintained by the daemon which reads its own file at start-up.

A Host other than the one on which the SD-UX commands are being executed.

Performing operations on remote systems from a single controller system. Remote operations must be enabled. (Also called centralized management or single point administration.) See Chapter 6 “Remote Operations Overview” for more information.

Refers to the operations with Agents on a remote computer.

An interactive control script that gets a response from the user. A request script prompts the user for a response, reads the user's answer, and stores the results in a response file. Request scripts can be run by the swask, swconfig, and swinstall commands.

A file that is generated by an interactive request script and contains the user's response.

This keyword defines the "revision" attribute for the product object. The revision information (release number, version) for the product.

The root directory of a system (/). See Root Directory.

The directory on a target host in which all the files of the selected products will be installed. The default (/), can be changed to install into a directory that will eventually act as the root to another system. See Alternate Root Directory.

Remote Procedure Call. DCE technology for distributed communications and data transfer.

The command that invokes the Job Browser, a GUI program that lets you create, monitor, schedule, and delete jobs. The swjob command lets you monitor jobs from the command line. You can also activate the Job Browser with the swjob -i command.

See SD-UX format.

The format and syntax of SD-UX software in depots. See Layout_version.

In SD-UX security, a password used to verify the authenticity of the caller's host. SD-UX manages sets of hosts by restricting and changing the default secret on all controller and target hosts in the network. See shared secrets file.

Controlling access to software objects. In SD-UX, security is achieved by a combination of Access Control Lists (ACLs) associated with objects and commands, and the security inherent in the file system permissions on which the software is stored. See Access Control List.

The first phase of a software installation, copy, remove, or verify operation, during which the user selects the software products to be installed, copied, or removed from the host.

A system on the network that acts as a software source for other systems on the network.

An HP program that permits central management of many system administration functions. You can run SD-UX from SCM.

Each invocation of a SD-UX command defines a session. Most SD commands let you use the
-C session_file option to save command options, source information, software selections, and host selections and re-use this information with the
-S session_file option. You can also save and re-use session information from the GUI programs.

In SD-UX security, a file containing the passwords used to encrypt and decrypt distributed communications for added security.

The ability to simultaneously distribute to, manage, or monitor multiple remote targets from a single controller system. See remote management.

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

An input file of previously defined software selections to be used as operands for a command. You specify a software file with the
-f software_file command line option.

A group of software selections read or saved from the GUI programs.

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

A group of
software objects that you have selected for an operation. You can save these software selections for later re-use. See software group.

A GUI window that lets you select the software files you want to install, copy, or remove.

A depot used as the source of a swinstall or swcopy operation.

See software source.

See Single Point Administration.

See staging.

A way of setting up intermediate depots that are local to each group of targets on local area networks. This can reduce the amount of network traffic.

An attribute that indicates the current state of the fileset. During installation, software is transitioned through the following states: non-existent, transient, installed, and configured. During removal, software is transitioned through these states: configured, installed, transient, and non-existent. If a task fails during a transient state, the state is set to corrupt.

An optional grouping of filesets, used to partition a product that contains many filesets or to offer the user different views of the filesets.

The state in which a patch was applied but was then replaced by a superseding patch. Other patch states include applied and committed.

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

A software product that provides all of the SD-UX functionality. SW-DIST is included on your HP-UX 11i media. If SW-DIST is damaged, missing, or corrupted on your system, you cannot install or copy any HP-UX software that is packaged in the SD-UX format, including a newer SW-DIST product. You can re-install SD-UX with the install-sd command.

A SD-UX command that allows you to modify Access Control List permissions that provide software security.

In SD-UX security, the default user identification group.

The SD-UX agent program that makes changes to depots and roots. It is directed by the controller and scheduled by the daemon

The SD-UX daemon that provides various services, including: initiation of communication between the controller and agent; serving one or more depots to multiple requesting agents on remote hosts.

A SD-UX command that lets you run an interactive request script to get a response from the user. Request scripts can also be run by the swconfig and swinstall commands.

A SD-UX command that configures previously installed software and make the software ready for use.

A SD-UX command that copies software from a software source to a depot or from one depot to another. The swcopy command can add products to an existing depot, replace products already on a depot, or create a new depot.

A SD-UX command used in previous HP-UX releases to install the new SW-DIST product from media. This command has been replaced by install-sd and update-ux.

A SD-UX command that installs software. swinstall may also perform software configuration.

A SD-UX command that lists software objects, their attributes, and their organization. It lists both installed software and software contained within a depot.

A file that contains the read or write access to software objects and ACLs.

A SD-UX command that lets you change information in the installed products database or depot catalog files.

A SD-UX command that uses a product specification file (PSF) to organize software products and package them into a depot. The depot can be accessed directly by SD-UX commands or mastered onto CD-ROM or tape.

A SD-UX command used to register or unregister depots.

A SD-UX command that removes previously installed software or removes packaged software from a depot.

A SD-UX command that verifies installed software or depot software for correctness and completeness.

Computers, either stand-alone or networked to other computers. See local host.

In packaging, a keyword that defines the distribution tag or software object's name attribute for the destination depot (media).

A software depot stored in a tar (tape archive) format. Within the archive, directory and file entries are organized using the same structure as any other SD-UX format depot.) Tape depots such as cartridge tapes, DAT and 9-track tape are referred to by the file system path to the tape drive's device file.

Software media that uses tar to store SD-UX software products and control files. It usually resides on a serial media such as a DDS, cartridge, nine-track, or other tape, though it can also be a regular file that contains the tar archive. Within the tar archive, directory and file entries are organized using the same structure as any other depot.

See tape depot.

Any system on which software is to be installed or managed with SD-UX. There are typically multiple targets on a network, identified by system name, network address, user name, or by a user group. Targets can contain a primary root, an alternate root, or depots. A target may also be the object of remote operations.

Most SD-UX commands let you use the
-t target_file option to read a list of previously defined target selections as operands for the command. You can also read or save target group files from the GUI programs when remote operations are enabled.

A group of systems or software objects that you have selected as targets for an operation. You can save these selections for later re-use. See target group.

A one-line, full name attribute that identifies the product with a title.

Terminal user interface. A character-based display with windows and pull-down menus that works on ASCII terminals. The TUI uses the keyboard to navigate (no mouse). See also Command Line User Interface and Graphical User Interface.

See Terminal User Interface.

User Datagram Protocol. Comparable with TCP/IP, but runs connections less and is intended to be used in more reliable network environments (LAN).

When a target is contacted for a software management operation, the system's four uname attributes (operating system name, release, version and hardware machine type) are obtained. Used to determine software compatibility with the proposed host.

An optional script that undoes the configuration done by the configure script. Unconfigure scripts are associated with filesets and are automatically executed by swremove before the removal of filesets begins. You can also run unconfigure scripts with swconfig.

Using the swreg command to remove the registration of a depot. This makes the depot unavailable to network access.

Overwriting software objects already installed on the system and replacing them with new objects.

A command that automates part of the HP-UX update process. It replaces the swgettools script used in previous versions of SD-UX. The install-sd updates the SD-UX product without performing an OS update.

The user (or host system for agents making remote procedure calls (RPCs) to other agents) that is originating the RPC call.

In packaging, a keyword that for the vendor object. Useful for NetLS vendors and for those who want to select products from two vendors who have chosen the same vendor_tag.

If a vendor specification is included in the PSF, swpackage requires the vendor and tag keywords.

Associates the product or bundle with the last-defined vendor object, if that object has a matching tag attribute.

A listing that is used to display all attributes for products, subproducts, filesets, or files.