NonStop NS-Series Database Migration Guide

Migrating SQL/MP, SQL/MX, and Enscribe
Applications
HP Integrity NonStop NS-Series Database Migration Guide—540469-001
4-7
SQL Compilation
the new system, and omit or change the node name in the DEFINE name mappings of
your script files.
Before you move embedded SQL/MP programs to an Integrity NonStop NS-series
system, set up commands or scripts on the TNS/E system to reestablish DEFINE
names for proper object name resolution.
To ensure proper resolution of DEFINE names, you do not need to SQL compile each
program that uses DEFINEs because these programs use the run-time DEFINEs that
you set in the execution environment of the TNS/E system. However, to ensure optimal
query execution plans and prevent automatic recompilation, explicitly SQL compile all
embedded SQL/MP programs on the TNS/E system. For more information, see SQL
Compilation on page 4-7.
For more information about database object names, see the SQL/MP Reference
Manual. For information about object name resolution, see the SQL/MP Installation
and Management Guide.
SQL Compilation
After you move and recompile or accelerate embedded SQL/MP programs on an
Integrity NonStop NS-series (or any new) system, you must SQL compile the programs
to ensure optimal query execution plans. For more information, see one or more of
these references:
•
SQL Programming Manual for TAL
•
SQL/MP Programming Manual for C (for pTAL programs that call embedded
SQL/MP routines written in the C language)
Embedded SQL/MP and SQL/MX Programs in
C, C++, and COBOL
When migrating embedded SQL/MP and SQL/MX programs to an Integrity NonStop
NS-series system, follow these guidelines:
•
TNS/R Native Object Files of Embedded SQL Programs on page 4-7
•
TNS Object Files of Embedded SQL Programs on page 4-8
•
Object Name References and Resolution on page 4-8
•
SQL Compilation on page 4-9
TNS/R Native Object Files of Embedded SQL Programs
TNS/R native object files (type 700) use process, memory, and RISC architectures that
are native to MIPS microprocessors and cannot run on TNS/E systems, which use
Itanium microprocessors. To migrate TNS/R native applications to TNS/E systems, you
must generate TNS/E native object files (type 800) either by using the ETK connected