SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Converting SQL/MP Applications to SQL/MX
Applications
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
10-7
Converting ODBC Client Applications to NonStop
SQL/MX
2. Correct all unsupported syntax in the source files. For details, see:
•
Using ETK to Detect Unsupported SQL Syntax on page 10-7
•
Changes to SQL Syntax on page 10-16
•
Changes to Embedded SQL Constructs on page 10-41
3. Preprocess and compile the source files. For details, see:
•
Development Environments for SQL/MX Applications on page 10-54
•
Similarity Checks and Automatic Recompilation of Embedded SQL/MX
Applications on page 10-55
•
Managing Modules of Embedded SQL/MX Applications on page 10-58
After converting SQL/MP applications to NonStop SQL/MX, you can continue to query
tables that remain in your SQL/MP database.
Using ETK to Detect Unsupported SQL Syntax
The HP Enterprise Toolkit—NonStop Edition (ETK) provides a quick and easy way to
detect and correct unsupported syntax when converting an SQL/MP application to
NonStop SQL/MX. Follow these steps in ETK:
1. Use the NonStop SQL/MX project wizard to start a new empty SQL/MX project.
2. Open your existing SQL/MP project and copy all the project source files, changing
the file extensions to ones that are supported by the host language and by
NonStop SQL/MX. For more information, see the
SQL/MX Programming Manual
for C and COBOL.
3. For SQL/MP statements that are incompatible with NonStop SQL/MX, add toggles
as needed to resolve the incompatibilities.
4. Build the project and add more toggles, if needed.
For information about using ETK, see the ETK online help.
Converting ODBC Client Applications to NonStop SQL/MX
If you want an ODBC client application, which uses NonStop SQL/MP, to take
advantage of SQL/MX functionality, you must migrate from the NonStop ODBC Server
environment to the HP NonStop SQL/MX connectivity services (MXCS) environment.
MXCS uses an ODBC 3.5 compliant API driver. For details about migrating to MXCS
server and client environments, see the
SQL/MX Connectivity Service Manual.
When migrating your ODBC client application to MXCS, you must modify the SQL
statements in the application to comply with SQL/MX syntax. For more information, see
Changes to SQL Syntax
on page 10-16.