Manualshelf

SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

ManualsBrandsHP ManualsServerHP Integrity NonStop H-Series
41424344454647484950
Version Management and Interoperability
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
3-4
Naming Scheme for SQL/MX Releases
Major and Incremental Releases
Major releases introduce significant new functionality. These releases occur less
frequently and usually require you to take specific action to use the new functionality,
such as perform an upgrade operation or alter existing applications.
Incremental releases introduce incremental changes and some new functionality,
which does not significantly affect existing applications.
In this manual, the SQL/MX releases are identified by major and incremental release
numbers, such as SQL/MX Release 2.3.4 and SQL/MX Release 3.0.
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 NonStop™ BladeSystems, 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).
TNNNNPNN_DDMMMYYYY_SPR_RRR_MMDD