NonStop NS-Series Database Migration Guide

HP Integrity NonStop NS-Series Database Migration Guide—540469-001
4-1
4
Migrating SQL/MP, SQL/MX, and
Enscribe Applications
You can migrate your SQL and Enscribe applications independently of the database or
while migrating the database. For example, you might move specific applications to the
Integrity NonStop NS-series system as part of a phased migration and test the
applications extensively on the new system before migrating the production database.
Or, you might choose a method of migration that involves some downtime during which
you move both the database and all applications to the Integrity NonStop NS-series
system at the same time. Specific migration approaches depend on your database
environment and business needs and are not covered in this subsection.
This section describes guidelines for migrating these types of applications to an
Integrity NonStop NS-series system:
•
ODBC Applications on page 4-1
•
Enscribe Applications on page 4-2
•
TAL and pTAL Programs That Use Embedded SQL/MP on page 4-5
•
Embedded SQL/MP and SQL/MX Programs in C, C++, and COBOL on page 4-7
•
Java Applications That Use JDBC/MX or JDBC/MP on page 4-9
•
SQLJ Applications on page 4-11
•
Stored Procedures in Java (SPJs) on page 4-11
For more information about application migration, see the H-Series Application
Migration Guide.
ODBC Applications
The process of migrating ODBC applications from a NonStop S-series system to an
Integrity NonStop NS-series system is rather straightforward and does not involve the
TNS/R and TNS/E system considerations required to migrate other application types
described in this section.
For information about migrating applications from the NonStop ODBC Server
environment to the NonStop SQL/MX connectivity services (MXCS) environment, see
the SQL/MX Connectivity Service Manual.
For information about migrating from SQL/MX Release 1.8 to SQL/MX Release 2.x,
including ODBC metadata migration, see the SQL/MX Database and Application
Migration Guide.