MX Database and Application Migration Guide

Version Management and Interoperability

HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001

2-4

Naming Scheme for SQL/MX Releases

Maintenance Releases

Maintenance releases introduce bug fixes and minimal new functionality. These

releases occur most frequently and rarely affect all the component products in the

SQL/MX product set. This manual refers to maintenance releases only when they

introduce new functionality that requires mentioning.

SQL/MX Product T-Numbers and VPROC Information

In a given SQL/MX release, participating SQL/MX products include the product version

identifier in their T-numbers (for example, T1051H30).

The VPROC information of each SQL/MX product in a given release is:

where:

TNNNNPNN

is the product T-number (for example, T1051) and the product version identifier

(

PNN). The first letter P in PNN represents the RVU series to which the product

version applies:



H for HP Integrity NS-series systems, which run H-series RVUs



J for HP Integrity HP NonStop BladeSystem, which run J-series RVUs

The next two digits

NN represent the SQL/MX release number (for example, 30 for

SQL/MX Release 3.0).

DDMMMYYYY

is the VPROC date (for example, 14FEB2011).

SPR

is the three-digit SPR identifier of the release (for example, ACF). For an initial

PVU, this field is the same as the product version

PNN (for example, H30).

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).

TNNNNPNN_DDMMMYYYY_SPR_RRR_MMDD