SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)

MMDD
is the final build date for the product, including the month and day (for example,
1130 for November 30).
For example, this VPROC command displays information for the T1051 product that is associated
with SQL/MX Release 3.0.0 for H-series RVUs:
T1051H30_14FEB2011_H30_300_1130
The SQL/MX Master Softdoc (T0650) for each SQL/MX release refers to the release name and
VPROC information.
Product version and SPR identifiers
Each SQL/MX release is associated with a product version identifier and possibly an SPR identifier.
Each product version identifier (for example, “H30”) includes:
• Supported platform of the product using “H” for systems running H-series RVUs or J-series
RVUs.
• SQL/MX release number (for example, “30” for SQL/MX Release 3.0)
For an initial product version (PV) of SQL/MX, the product version identifier is not accompanied
by an SPR identifier. For example, the initial PV of SQL/MX Release 3.0 on systems running H-series
RVUs is referred to as “H30.”
For a product version update (PVU) of SQL/MX, the product version identifier is accompanied by
an SPR identifier. For example, the PVU of SQL/MX Release 3.0 on systems running H-series RVUs
is referred to as “H30^ACF” where “ACF” is the SPR identifier.
Availability of SQL/MX releases
Each SQL/MX release is made available to customers as a General Availability (GA) release, a
Controlled Availability (CA) release, or an Early Adopter Program (EAP) release.
A GA release is available to any customer who orders the product and whose system meets the
prerequisites for using the product.
A CA release limits the shipment of a product to a set of customers who agree to specific use
conditions, which include migrating to a GA release when it is ready.
An EAP release introduces a new product to customers at a very early stage and is a type of test
program conducted at a customer site.
For more information about these types of releases, see the Managing Software Changes Manual.
Delivery of SQL/MX releases
Each SQL/MX release is delivered as a set of Software Product Revisions (SPRs). Some SQL/MX
SPRs are first available for downloading from Scout for NonStop Servers and are later available
on the next RVU’s site update tape (SUT). Other SQL/MX SPRs are available only on specific RVU
SUTs and are not available in Scout for NonStop Servers. Rarely, as is the case for SQL/MX
Release 3.0 (H30), which is an Early Product Delivery (EPD), the SQL/MX SPRs must be ordered
in Scout for NonStop Servers as a backup tape delivery.
For more information about the delivery of SQL/MX Release 3.2, see Table 4 (page 60). To learn
how to acquire a SQL/MX release that is not listed in those tables, check the SQL/MX Master
Softdoc (T0650) for that SQL/MX release.
RVUs and supported SQL/MX releases
Each SQL/MX release is supported by specific Release Version Updates (RVUs). An RVU is a
collection of compatible revisions of HP NonStop operating system software products that are
shipped and supported as a unit.
Before downloading a set of SQL/MX SPRs from Scout for NonStop Servers, verify that the RVU
of your system supports that release of SQL/MX. For more information, see Table 4 (page 60).
62 Version management and interoperability