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

Preparing TNS and TNS/R Object Files of Enscribe

Applications To Access SQL/MP Tables

37> escort

Escort Command Interpreter - Version 1.7.0 - 01MAY2005 - System

\NSKNED

Escort 1? PREPARE OGET , LIBRARY libname;

--- $PRPC.TEST.OGET preparation complete

--- Escort SQL User Library $DATA.ESCORT.ESCRUNTM

Because the Escort command interpreter supports the use of wildcards, entire

subvolumes can be prepared with a single command.

ESCRUNTM, the Escort SQL runtime library for TNS programs, contains prepared

copies of C, C++, COBOL, and pTAL runtime libraries. If a TNS program currently calls

a procedure in the system library routine, the calls are automatically retargeted to the

ESCRUNTM user library at execution time if ESCRUNTM contains the same

procedure.

Example: Preparing a TNS/R Object File After Rebuilding It As a TNS/E

Object

Because the Integrity NonStop NS-series system does not support TNS/R objects,

they must first be converted to TNS/E objects by the TNS/E compilers on the new

system. After they are recompiled, you prepare the objects to use the Escort DLL

ESCRUNDL, as shown in this example.

26> escort

Escort Command Interpreter - Version 1.7.0 - 01MAY2005 - System

\DRPSOC

Escort 1? PREPARE EGET;

--- $DATA5.TEST.EGET preparation complete

--- Escort SQL DLL $DATA.ESCORT.ESCRUNDL

In TNS/E programs, the retargeting of system procedure calls is performed in the same

manner as it is for TNS object files.

However, because the Escort SQL runtime for TNS/E programs is implemented as a

DLL instead of a user library, the PREPARE command simply sets ESCRUNDL, the

Escort SQL runtime DLL, as a DLL for the program.

Combining the Escort SQL Runtime Library With Custom

User Libraries

If the Enscribe application uses a custom runtime library, you must combine it with the

Escort SQL runtime library.