MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Version Management and Interoperability

HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002

3-5

Product Version and SPR Identifiers

RRR

is the three-digit SQL/MX release number (for example, 300 for SQL/MX Release

3.0.0).

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 NonStop 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 NonStop 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. For

example, the SQL/MX DDL license (T0394) has controlled availability for current

SQL/MX releases.