The service functions in the UAP shared library can be loaded (read) dynamically. Service functions can be added or deleted from an SPP simply by changing the definition. The UAP shared library is created by linking the set of UAP object files generated by compiling the UAP source files.

When you load service functions dynamically, you can add or delete service functions simply by changing the service operand of the user service definition without having to change the stub or re-create the UAP's executable file. Because the service functions are loaded when the UAP starts, no stub or service functions are needed in order to create the UAP's executable file. Also, because no RPC interface definition is required, there is no need to re-create the UAP's executable file when adding a new service to or deleting a service from an existing UAP.

Because dynamic loading of service functions saves work, it is particularly useful in a system where services are frequently added or deleted.

Note

Dynamic loading of service functions is applicable only to SPPs and MHPs, except in the following cases:

• The user server uses the XATMI interface.
• The TP1/Offline Tester is being used.

Organization of this section

3.8.1 Examples of using dynamic loading of service functions

3.8.2 Preparation required for using dynamic loading of service functions