H-Series Application Migration Guide (H06.03+)

TNS/E Native Architecture Features
H-Series Application Migration Guide—429855-006
3-8
TNS/R PIC Migration Considerations
converted from SRLs to DLLs, such as compiler run-time libraries, have new names,
which means that build scripts that reference these libraries must be changed. See
TNS/E Native Run-Time Libraries on page 2-6 for the new library names.
If your application uses a user library (private SRL), you must rebuild the user library
as a DLL. See Section 8, User Library Migration Tasks, for information on migrating
user libraries.
The use of DLLs in an application can improve the performance and efficiency of the
application. In addition, DLLs are easier to create and maintain than SRLs.
TNS/R PIC Migration Considerations
TNS/E DLLs have all the functionality of TNS/R DLLs plus some additional
functionality. As with programs, they must be recompiled with a TNS/E native compiler
and relinked with the TNS/E linker eld when migrating to an H-series system. The eld
linker is functionally equivalent to the TNS/R PIC linker ld and provides the same
features and options. To migrate a TNS/R DLL:
1. Recompile the DLL components using a TNS/E native compiler. You do not need
to specify an option to generate PIC object files because the TNS/E compilers
generate only PIC.
2. Build the DLL using the eld linker.
In the G06.2x RVUs, libraries supplied by HP, such as compiler run-time libraries, are
packaged as a special type of SRL called a hybrid SRL, which can be accessed by
both PIC and non-PIC programs. On H-series systems, these hybrid SRLs have been
converted to DLLs. These DLLs have new names, which means that build scripts that
reference the libraries must be changed. See TNS/E Native Run-Time Libraries on
page 2-6 for the new library names.