NonStop NS-Series Database Migration Guide

Migrating SQL/MP, SQL/MX, and Enscribe
Applications
HP Integrity NonStop NS-Series Database Migration Guide540469-001
4-3
TNS Object Files of Enscribe Applications
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.
TNS Object Files of Enscribe Applications
Enscribe applications in C, C++, COBOL, and pTAL might be TNS object files (type
100). Enscribe applications in TAL and FORTRAN are always TNS object files. TNS
object files use complex instruction-set computing (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 Object Code Accelerator (OCA) on the TNS/E system. The OCA enables you
to optimize TNS programs to run faster on TNS/E systems. For more information, see
the Object Code Accelerator (OCA) Manual. 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.
Preparing TNS and TNS/R Object Files of Enscribe Applications
To Access SQL/MP Tables
Preparing the Enscribe Applications
When you use Escort SQL to migrate an Enscribe database on a NonStop NS-series
system to an Integrity NonStop NS-series system as described in Converting Enscribe
Data and Applications to SQL/MP on the New System on page 3-1, you need to
prepare the TNS and TNS/R object files of the migrated Enscribe applications so that
the programs can access the SQL/MP tables. You do this by issuing the Escort SQL
PREPARE command from the Escort SQL command interface to:
Update the object file’s procedure identifier list (PIL) to rename references to
Enscribe I/O calls to Escort SQL runtime library procedures.
Set the user library of the program to the Escort SQL runtime. If the program
already has a user library, the PREPARE command does not change the library,
but instead ensures that the Escort SQL runtime is bound to it.
Example: Preparing a TNS File Object File
This example uses the PREPARE command to prepare a TNS object file to use the
Escort TNS (code 100) ESCRUNTM.
To compile these programs on a TNS/E system... See...
C and C++ programs C/C++ Programmer’s Guide
COBOL programs COBOL Manual for TNS/E
Programs
pTAL programs pTAL Reference Manual