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-11

Default Heap and Stack Sizes

The default heap and stack sizes are larger on TNS/E systems. For more information,

see the NonStop Server for Java Programmer’s Reference for SDK 1.4.2.

CLASSPATH and _RLD_LIB_PATH Environment Variables

Before migrating your JDBC/MX applications to an Integrity NonStop NS-series

system, you must install and configure the appropriate versions of the NonStop Server

for Java and JDBC/MX driver on the system. The CLASSPATH environment variable

must refer to the path of the H-series JDBC/MX JAR file, jdbcMx.jar. The

_RLD_LIB_PATH environment variable must refer to the H-series JDBC/MX native

library, libjdbcMx.so, which is in TNS/E PIC object format. For more information,

see the T1275 Softdoc file on the NonStop Server for Java 4 product CD.

SQLJ Applications

SQLJ applications are not supported on TNS/E systems. If you have SQLJ applications

and want to use them on a TNS/E system, you must convert the SQLJ applications to

JDBC/MX applications:

1. Change the .sqlj source files to .java files.

2. In the source code, convert the SQLJ clauses to JDBC/MX method calls.

3. Compile the source code by using the javac compiler.

For more information about JDBC/MX, see the JDBC Driver for SQL/MX Programmer’s

Reference.

Stored Procedures in Java (SPJs)

To migrate SPJs to an Integrity NonStop NS-series system:

1. Move the class files that contain the SPJ methods and all supporting classes to the

OSS environment of the TNS/E system.

2. Register the stored procedures in the SQL/MX system metadata by issuing

CREATE PROCEDURE statements.

For more information, see the SQL/MX Guide to Stored Procedures in Java.

The same migration issues that affect other Java applications apply to SPJ classes.

For more information, see Java Applications That Use JDBC/MX or JDBC/MP on

page 4-9.

To ensure that the TNS/E system is configured to support SPJs, see the SQL/MX

Guide to Stored Procedures in Java.