Managing Serviceguard Fifteenth Edition, reprinted May 2008

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4178
If a resource is configured to be AUTOMATIC in a legacy configuration file,
you do not need to define DEFERRED_RESOURCE_NAME in the package
control script.
About Package Dependencies
Starting in Serviceguard A.11.17, a package can have dependencies on
other packages, meaning the package will not start on a node unless the
packages it depends on are running on that node.
In Serviceguard A.11.17, package dependencies are supported only for
use with certain applications specified by HP, such as the multi-node and
system multi-node packages that HP supplies for use with Veritas
Cluster File System (CFS) on systems that support it.
As of Serviceguard A.11.18, package dependency is no longer restricted;
you can make a package dependent on any other package or packages
running on the same cluster node, subject to the restrictions spelled out
in Chapter 6, under dependency_condition (see page 294).
Make a package dependent on another package if the first package
cannot (or should not) function without the services provided by the
second. For example, pkg1 might run a real-time web interface to a
database managed by pkg2. In this case it might make sense to make
pkg1 dependent on pkg2.
In considering whether or not to create a dependency between packages,
consider the Rules and Guidelines that follow.