DLL Programmer's Guide for TNS/E Systems

DLLs on a TNS/E System
DLL Programmer’s Guide for TNS/E Systems—527252-006
1-9
The TNS/E Library Facility
For the loadfiles in Figure 1-4:

The program indirectly references D, E, F, and G, so these libraries do not appear
in the program’s libList.

The program’s loadList comprises all the libraries shown in the figure.

A indirectly references G, and A’s loadList comprises D, E, and G.
Neither a loadfile nor its programmer needs to know about its indirect needs. There is
no limit to the number or depth of directly and indirectly referenced libraries in a
loadList. Also, many libraries in the loadList can reference the same library, as
illustrated by the multiple clients of F and G. Each library appears once in the loadLIst
and in memory.
The TNS/E Library Facility
This subsection gives an overview of the library facility and some of the controls it
offers. Discussion of how to control the library-facility begins in Essential DLL Facility
Controls on page 2-1.
Public Libraries and DLLs (Implicit and Explicit).
TNS/E supports public libraries. Public libraries are a set of (DLL) libraries, available to
all users of the system, and managed as part of the system software. They are mostly
supplied by HP, although you and third party software providers can also provide DLLs
to be added to the public DLLs. You use DSM/SCM to add your DLLs to the public
libraries. Note that these must be loadfiles, not linkfiles.
Public libraries include:
Figure 1-4. Loadfiles and Their libLists (To Create the Structure in Figure 1-2)
Program
DLL A
DLL B
DLL C
DLL D
DLL E
Lib G
Lib F
Lib A
Lib B
Lib C
Lib F
Lib D
Lib E
Lib F
Lib G
Lib G
Code
and
Data
libList
VST014.vsd