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-8
TNS Object Files of Embedded SQL Programs
to a TNS/E host or by compiling the source code directly on the TNS/E system. You
might need to make some minor changes to the source code before compilation. For
details on required source code changes, see the H-Series Application Migration
Guide.
To compile embedded SQL/MP and SQL/MX programs on a TNS/E system, see:
•
SQL/MX Programming Manual for C and COBOL (SQL/MX C and COBOL
programs)
•
SQL/MP Programming Manual for C (SQL/MP C programs)
•
SQL Supplement for H-Series Servers (SQL/MP COBOL programs)
TNS Object Files of Embedded SQL Programs
TNS object files (type 100) use CISC instructions and can usually be interpreted or
accelerated on TNS/E systems without recompiling the source code.
After migrating TNS applications to a TNS/E system, accelerate the object files by
using the OCA on the TNS/E system. See the information about running the
accelerator for cross-platforms in the SQL/MP Programming Manual for C and the
information about acceleration of TNS HP COBOL programs in the SQL Supplement
for H-Series Servers. The OCA enables you to optimize TNS programs to run faster on
TNS/E systems. However, for greater performance gains, HP recommends that you
convert TNS applications to native mode. For more information, see the TNS/E Native
Application Conversion Guide.
Object Name References and Resolution
Embedded SQL/MP and SQL/MX programs that query SQL/MP databases refer to
SQL/MP database objects by their Guardian file names, DEFINE names, or SQL/MP
aliases (SQL/MX programs only). Verify that the Guardian file names in the source
code, in DEFINE name mappings, or in SQL/MP alias mappings do not specify the
node name, which might change when you move the database to an Integrity NonStop
NS-series (or any new) system. If necessary, omit or change the node name in the
source code and then recompile on the new system, and omit or change the node
name in the DEFINE name mappings or the SQL/MP alias mappings of your script
files.
Before you move embedded SQL programs to an Integrity NonStop NS-series system,
set up commands or scripts on the TNS/E system to re-create SQL/MP aliases (for
SQL/MX programs only) and to reestablish DEFINE names for proper object name
resolution.
To ensure proper resolution of SQL/MP aliases, explicitly SQL compile each program
that uses aliases on the TNS/E system. Otherwise, these programs might refer to
database objects on the NonStop S-series system.
Note. TNS/E systems do not support TNS mode compilation in the OSS environment. If you
have TNS OSS files, you must convert them to TNS/E native mode.