Managing Software Changes (G06.24+)

Managing Software Changes—427169-003
Glossary-1
Glossary
CA. See Controlled Availability (CA).
conditional requisite. A requisite that is needed only under certain circumstances.
Content file. A file listing the SPRs included in and excluded from a release version update
(RVU).
Controlled Availability (CA). Conditional release of a product that does not meet a
published standard or which HP does not support under published policy. CA releases
are used to limit the shipment of a product or a release version update (RVU) to a set
of customers who agree to specific usage conditions, which include migrating to the
General Availability (GA) release when it is ready.
direct requisite. A requisite that is cited in the softdoc addendum of the requiring SPR.
Distributed Systems Management/Software Configuration Manager (DSM/SCM). A
graphical user interface (GUI)-based program that installs new software and creates a
new operating system. DSM/SCM creates a new software revision and activates the
new software on the target system.
distribution subvolume (DSV). A subvolume containing program files for a particular
software product revision along with the software release document (softdoc) file for
that SPR. The format for a DSV name is Ynnnnrrr or Rnnnnrrr, where nnnn is the
software product number, and rrr is the product version suffix (such as D40) or product
version update (PVU) suffix (such as AAB).
DSM/SCM. See Distributed Systems Management/Software Configuration Manager
(DSM/SCM).
DSV. See distribution subvolume (DSV).
EAP. See Early Adopter Program (EAP)
.
Early Adopter Program (EAP). A program for introducing a new release series or a new
product to customers at a very early stage. An EAP is a type of test program
conducted at a customer site. HP might make the products participating in the EAP
available to a specific customer to satisfy a customer commitment. EAP releases are
not generally used in production systems.
emergency overlay. A change made to a release version update (RVU) to correct a defect
that potentially could have severe consequences, such as data corruption, application
outage, or unusable subsystems, for multiple customers. The correction is applied to,
or overlaid on, the master copy of each RVU in which the defect is present and is
included in all subsequent distributions of those RVUs. The emergency overlay action
is announced by a Hotstuff message within 24 hours of its completion.