To set up dynamic loading of service functions:

1. Create a UAP shared library from the service functions.
2. In the service operand of the user service definition, specify the service names, entry point names, and UAP shared library name.

For details about the service operand, see the manual OpenTP1 System Definition.

Table 3-18 describes whether the UAP object needs to be relinked after a service function is added.

Table 3-18 Criteria for relinking UAP objects

No.	UAP object in which a service is added or deleted	Service added by	Relink
1	UAP object that uses only the RPC interface definition	Using the RPC interface definition	Yes
		Using dynamic loading of service functions	No
2	UAP object that uses only dynamic loading of service functions	Using the RPC interface definition	Yes
		Using dynamic loading of service functions	No
3	UAP object that uses both the RPC interface definition and dynamic loading of service functions	Using the RPC interface definition	Yes
		Using dynamic loading of service functions	No

Legend:

Yes: The UAP object must be relinked.

No: The UAP object does not need to be relinked.