Library Sub-Package

A profile must be attached to a profile library before it can be used (and it can be attached to only one library). There are two kinds of profile libraries: local and public. A local profile library exists as part of a network model. When you create a local profile, it is added automatically to the local profile library and stored as part of the network. A public profile library is a separate, named model that is stored in your primary model directory and can be used by any network model.

Local profile libraries exist automatically as part of a network model and are always opened and saved with the network model. Public profile libraries, however, must be explicitly created and opened for access. To create a public profile library, use prg_profile_lib_create(). You can save a public profile library with prg_profile_lib_write(). To open a public profile library for access, use prg_profile_lib_open() (note that newly created libraries are already open). When you no longer need a public profile library, close it with prg_profile_lib_close().

To add a profile to a profile library, local or public, use the function prg_profile_lib_profile_add(). Profiles are automatically removed from local profile libraries when they are no longer referenced by any network objects. To remove a profile from a public profile library, use either prg_profile_lib_profile_named_remove() or prg_profile_lib_profile_nth_remove().

You can get information about a profile library with several functions:

Finally, you can load a profile from a profile library (for access using Data sub-package functions) with prg_profile_lib_profile_named_load() or prg_profile_lib_profile_nth_load().