HP Serviceguard Version A.11.18 Release Notes, September 2008

IMPORTANT: These rules apply to both legacy and modular packages. Restrictions
on the values of these parameters in previous Serviceguard releases were less
stringent. Packages that use values for these parameters that do not conform to
the new rules will continue to run, but if you reconfigure them, you will need to
change the values; cmcheckconf and cmapplyconf will enforce the new rules.
Migrating Legacy to Modular Packages
A new Serviceguard command, cmmigratepkg, provided with the patches listed
under “September 2008 Patch” (page 13), automates the process of migrating legacy
packages to modular packages as far as possible. Many, but not all, packages can be
migrated in this way; for details, see the white paper Migrating Packages from Legacy to
Modular Style at http://docs.hp.com ->High Availability ->
Serviceguard -> White papers.
NOTE: The cmmigratepkg command requires Perl version 5.8.3 or higher on the
system on which you run the command. It should already be on the system as part of
the HP-UX base product.
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 of Managing Serviceguard.
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.
For more information, see “About Package Dependencies” in Chapter 4 of Managing
Serviceguard.
About Multi-Node Packages
As of Serviceguard A.11.18, multi-node packages are no longer restricted to HP-supplied
applications; you can create a multi-node package for any purpose.
38 Serviceguard Version A.11.18 Release Notes