TNS/E Native Application Conversion Guide

TNS/E Native Application Conversion Guide—529659-003
6-1
6 Converting a TNS User Library
This section explains how to convert TNS user libraries to TNS/E native user libraries.
A user library is an object file that the operating system links to a program file at run
time. C, C++, COBOL, TAL, and pTAL programs can have a user library. There are two
types of user libraries on H-series systems: TNS user libraries and TNS/E native user
libraries. A TNS user library is available to TNS processes in the Guardian
environment. A TNS/E native user library is available to TNS/E native processes in the
Guardian and OSS environments.
A TNS/E native user library is a DLL that has a special relationship to a program. A
TNS/E native user library is architecturally identical to, and in most respects is treated
the same as, any other DLL. A program can have only one TNS/E native user library,
although it can load multiple ordinary DLLs.
This section discusses:
•
User Library Differences
•
Building a User Library
•
Specifying a User Library
User Library Differences
The following table summarizes the differences between TNS and TNS/E native user
libraries:
TNS User Libraries TNS/E Native User Libraries
Either or both the program file and user
library file can be accelerated (processed by
AXCEL, OCA, or both).
Both the program file and user library file
must be compiled with TNS/E native
compilers.
Can contain embedded SQL statements. Cannot contain embedded SQL statements.
Move functions with embedded SQL
statements to user code before converting a
TNS user library to a TNS/E native user
library.
Can call a limited subset of the C run-time
library.
Can call any function in the C run-time
library.
A COBOL user library specified at
compilation time can be overridden at run
time.
A COBOL user library specified at
compilation time cannot be overridden at run
time.