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-10
Object Name References
•
Default Heap and Stack Sizes on page 4-11
•
CLASSPATH and _RLD_LIB_PATH Environment Variables on page 4-11
Object Name References
For JDBC/MP applications, verify that the Guardian file names of SQL/MP database
objects, either in the source code or in a Properties object file, do not include the
node name, which might change when you move the database to an Integrity NonStop
NS-series (or any new) system. If the Guardian file name includes the node name,
change or omit the node name in the source code or Properties file and then
recompile the application. If you omit the node name, the SQL/MP driver uses the
current node to fully qualify the database object names. For more information, see the
JDBC Driver for SQL/MP Programmer’s Reference.
For JDBC/MX applications, verify that the mploc property, -Djdbcmx.mploc, does
not include the node name, which might change when you move the database to an
Integrity NonStop NS-series (or any new) system. If the mploc property includes the
node name, change or omit the node name in the mploc property and then recompile
the application. If you omit the node name, the SQL/MX driver uses the current node to
fully qualify the database object names. For more information, see the JDBC Driver for
SQL/MX Programmer’s Reference.
Java Native Interface (JNI) Changes
The JNI, which enables Java methods to call C and C++ methods, has undergone
changes on TNS/E systems. For example:
•
DLLs are used instead of static libraries.
•
C++ code can be compiled with a language dialect of version 2, version 3, or
neutral of the C++ run-time library.
•
The -Dcompaq.liblist option, the Makefile, and the JavaLibList file are no
longer used on TNS/E systems.
For more information, see the NonStop Server for Java Programmer’s Reference for
SDK 1.4.2.
Note. The NonStop Server for Java 4 on TNS/E systems has the same Java features and
functions as the NonStop Server for Java 4.2 on TNS/R systems. The JDBC/MX driver on
TNS/E systems has the same features and functions as the JDBC/MX driver V32 on TNS/R
systems. Before migrating JDBC/MX applications to an Integrity NonStop NS-series system,
consider migrating to Version 2 of the NonStop Server for Java 4 (SDK 1.4.2) and V32 of the
JDBC/MX driver on the TNS/R system. For more information, see migration instructions in the
NonStop Server for Java Programmer’s Reference and the JDBC Driver for SQL/MX
Programmer’s Reference, respectively.