Setting up HP SIM 5.x on an HP-UX Serviceguard Cluster (448492-002, January 2009)

# Enter the names of the dependency condition for this package.
# Dependencies are used to describe the relationship between packages
# To define a dependency, all three attributes are required.
#
# DEPENDENCY_NAME must have a unique identifier for the dependency.
#
# DEPENDENCY_CONDITION
# This is an expression describing what must be true for
# the dependency to be satisfied.
#
# The syntax is: <package name> = UP , where <package name>
# is the name of a multi-node or system multi-node package.
#
# DEPENDENCY_LOCATION
# This describes where the condition must be satisfied.
# The only possible value for this attribute is SAME_NODE
#
# NOTE:
# Dependencies can only be defined for packages within a CFS cluster.
These are
# automatically setup in the SYSTEM-MULTI-NODE and MULTI-NODE packages
created for
# disk groups and mount points. Customers configure dependencies for
FAILOVER type
# packages only; and the dependency would be on a MULTI-NODE mount point
(MP) package.
#
# Example :
# DEPENDENCY_NAME SG-CFS-MP-1
# DEPENDENCY_CONDITION SG-CFS-MP-1=UP
# DEPENDENCY_LOCATION SAME_NODE
#
#DEPENDENCY_NAME
#DEPENDENCY_CONDITION
#DEPENDENCY_LOCATION SAME_NODE
#
# Enter the SERVICE_NAME, the SERVICE_FAIL_FAST_ENABLED and the
# SERVICE_HALT_TIMEOUT values for this package. Repeat these
# three lines as necessary for additional service names. All
# service names MUST correspond to the SERVICE_NAME[] entries in
# the package control script.
#
# The value for SERVICE_FAIL_FAST_ENABLED can be either YES or
# NO. If set to YES, in the event of a service failure, the
# cluster software will halt the node on which the service is
# running. If SERVICE_FAIL_FAST_ENABLED is not specified, the
# default will be NO.
#
# SERVICE_HALT_TIMEOUT is represented as a number of seconds.
# This timeout is used to determine the length of time (in
# seconds) the cluster software will wait for the service to
# halt before a SIGKILL signal is sent to force the termination
# of the service. In the event of a service halt, the cluster
# software will first send a SIGTERM signal to terminate the
# service. If the service does not halt, after waiting for the
# specified SERVICE_HALT_TIMEOUT, the cluster software will send
# out the SIGKILL signal to the service to force its termination.
# This timeout value should be large enough to allow all cleanup
# processes associated with the service to complete. If the