TNS/E Native Application Conversion Guide

Introduction to Native Mode
TNS/E Native Application Conversion Guide—529659-003
1-18
Native Mode Conversion Considerations
PIC and DLLs were introduced in the G06.20 RVU. Non-PIC and SRLs continue to be
supported in the G06.2x RVUs. On H-series systems, all native code is PIC, and all
native libraries are DLLs. Non-PIC and SRLs are not supported. DLLs on H-series
systems include:
•
The system library, which is packaged as a set of implicit DLLs
•
Other libraries supplied by HP, such as compiler run-time libraries
•
All user-created libraries.
The TNS/E native compilers generate PIC object files (linkfiles), the TNS/E linker eld
creates executable loadfiles (programs or DLLs), and the loader and operating system
load and execute the results.
For more information about building and using DLLs, see the DLL Programmer’s
Guide for TNS/E Systems .
Native Mode Conversion Considerations
Code that is configured in the system library for TNS processes is packaged in DLLs
for TNS/E native processes. Public libraries, such as the C run-time library, the
COBOL run-time library, the TCP/IP sockets library, the Tools.h++ class library, and
the OSS API are also packaged as DLLs for TNS/E native processes. No code
changes are required to use these DLLs. Certain HP-supplied libraries that have been
repackaged as DLLs have new names, which means that build scripts that reference
these libraries will need to change.
If your application uses a TNS user library, that library must be rebuilt as a DLL. See
Section 6, Converting a TNS User Library, for more information.
Figure 1-2 on page 1-19 illustrates how code that is bound into TNS C programs or
configured in the system library is configured in DLLs for TNS/E native C programs.