ASAP 1.1 Hybrid Manual

HP NonStop ASAP Hybrid Manual – 529729-004
Page 4-4
 Optionally update data items for the domains. Single-threaded
applications would use the asap_update, asap_updatelist procedures, or
both. Multithreaded applications would use the asap_update_ts,
asap_updatelist_ts procedures, or both.
 Optionally update the operational state and text for the domains. Single-
threaded applications would use the asap_opstate procedure, and
multithreaded applications would use the asap_opstate_ts procedure.
 Optionally activate and deactivate ranking for the domains as needed.
Single-threaded applications would use the asap_control procedure, and
multithreaded applications would use the asap_control_ts procedure.
 Optionally determine the last sample time for a domain as needed. Both
single-threaded and multithreaded applications would use the
asap_getlastsampletime procedure.
 Remove all registered domains prior to shutting down. Single-threaded
applications would use the asap_remove procedure, and multithreaded
applications would use the asap_remove_ts procedure.
ASAP Hybrid for Linux API Libraries
ASAP Hybrid for Linux provides libraries for both 32-bit x86 and 64-bit AMD64
platforms, with static and shared variants of each. A given application must link
to one of these libraries, depending both on the platform you are developing for
and the system management strategy employed for your particular environment.
To establish which library to use, you must first determine the target platform for
your application. If you are developing a 32-bit application, you need to link to a
32-bit API library. If you are developing a 64-bit application, you need to link to
the 64-bit API library.
Once you determine the platform, you must decide whether to use the static
library or the shared library for that platform. Each type of library has its
advantages and disadvantages, depending on how you typically manage your
environment: