HP-UX IPQoS A.01.00 Programmer's Guide (October 2005)

Using the HP-UX IPQoS API
Using Sessions
Chapter 224
• IPQOS_STATUS_INACTIVE: The filter (or policy) object was created in the current session
and is not currently attached to a policy (or adapter) object.
• IPQOS_STATUS_ACTIVE_UPON_COMMIT: The filter (or policy) object was created in the
current session, is attached to a policy (or adapter) object and will become active in the
HP-UX IPQoS kernel module after IpqosCommitSession() is successfully called.
• IPQOS_STATUS_INACTIVE_UPON_COMMIT: The filter (or policy) object is attached to a policy
(or adapter) and is active in the HP-UX IPQoS kernel module, but will be deleted after
IpqosCommitSession() is successfully called.
These functions are useful in IPQOS_SESSION_CONFIG sessions to distinguish between objects
attached or deleted in the current session (and thus pending a commit) versus objects that
were previously configured.
Based on object status, there are some restrictions as to allowable functions to call. For
example:
• If the object status of a filter or policy object is not IPQOS_STATUS_INACTIVE, you can not
successfully call: IpqosAttachFilter() or IpqosAttachPolicy(). The functions will
return the code IPQOS_E_ALREADY_ATTACHED.
• If the object status of a filter or policy object is IPQOS_STATUS_INACTIVE, you can not
successfully call: IpqosDeleteFilter() or IpqosDeletePolicy(). The functions will
return the code IPQOS_E_NOT_ATTACHED.