SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—523723-004
11- 2
Migrating SQL/MP Applications to Release 2.x
•
Migrating Release 1.8 applications to run successfully in a Release 2.x
environment
In the first scenario, only C, C++, or COBOL applications would be migrated, not SQLJ
applications. SQLJ applications are not supported by an SQL/MP engine.
For information about migrating an entire database to the Release 2.1 or Release 2.0
environment, see Section 14, Migrating an SQL/MP Database to NonStop SQL/MX
Release 2.1 or Release 2.0.
Migrating SQL/MP Applications to Release 2.x
To migrate SQL/MP applications written in C, C++, or COBOL to a Release 2.x
environment, you need to:
•
Identify the source files being moved.
•
Correct all unsupported syntax in the source files.
•
Preprocess and compile them.
For information about source files and their extensions, see the SQL/MX Programming
Manual for C and COBOL. For information about syntax differences between SQL/MP
and SQL/MX applications, see the SQL/MX Comparison Guide for SQL/MP.
The HP Enterprise Toolkit—NonStop Edition (ETK) and similar tools provide a quick
and easy way to highlight unsupported syntax. For information about the ETK tool kit,
see ETK online help.
After migrating SQL/MP applications, you can query tables that remain in your SQL/MP
database from the Release 2.1 or Release 2.0 environment.
Migrating SQL/MX Applications From Release 1.8 to Release 2.x
You should be able to migrate and run Release 1.8 C, C++, and COBOL applications
in a Release 2.x environment without having to recompile them. However, you must
explicitly preprocess and compile any Release 1.8 C, C++, and COBOL application
that uses character data associated with the KANJI or KSC5601 character set when
you migrate it to run in a Release 2.x environment.
When you migrate Release 1.8 SQLJ applications to run in a Release 2.x environment,
you must recustomize and SQL compile them if any of these conditions applies:
•
You did not code a MODULE directive in the SQLJ application, or you coded it but
did not specify the NAMES ARE ISO88591 clause.
•
The SQLJ application queries floating-point data.
Caution. If you do not explicitly recompile the affected application, data corruption, or
application failure can occur.