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

TNS/E Native Architecture Features
H-Series Application Migration Guide—429855-006
3-7
TNS/R Non-PIC Migration Considerations
:
Specific migration tasks depend on whether the program consists of PIC or non-PIC.
See the DLL Programmer’s Guide for TNS/E Systems for more information about
building and using DLLs.
TNS/R Non-PIC Migration Considerations
No changes are required to TNS/R native programs that use public SRLs. On H-series
systems, all code is PIC. When you link your compiled TNS/E native programs, they
will be linked to the appropriate DLLs. Libraries supplied by HP that have been
Table 3-3. TNS/E and TNS/R Library Comparison
Library Type TNS/R Characteristics TNS/E Characteristics
Public library
•
Public libraries are implemented
as SRLs (pre-G06.20)
•
Public libraries are implemented
as hybrid SRLs (G06.20 and
later)
•
Libraries supplied by HP are
implemented as public SRLs
•
A process can have multiple
public SRLs
•
Programmers cannot create
public SRLs
•
Public libraries are
implemented as DLLs
•
Libraries supplied by HP are
implemented as public DLLs
•
A process can have multiple
public DLLs
•
Programmers can create
public DLLs
•
Public DLLs can contain
privileged code, provided that
the code meets security
requirements
Private library
•
Private libraries can be created
by programmers
•
Non-PIC characteristics:
°
Private libraries are
Implemented as SRLs
°
A process can have only
one private library (a user
library)
•
PIC characteristics (G06.20 and
later):
°
Private libraries are
implemented as DLLs
°
User library is a DLL
°
A process can have one
user library and can load
multiple ordinary DLLs
•
Private libraries cannot contain
privileged code
•
Private libraries can be
created by programmers
•
Private libraries are
implemented as DLLs
•
User library is a DLL
•
A process can have one user
library and can load multiple
ordinary DLLs
•
Ordinary DLLs can contain
privileged code, provided that
the code meets security
requirements