Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX Release README: B.06.00

the package directory will put the package in toolkit
maintenance mode.
Serviceguard 11.19 release has a new feature which allows
individual
components of the package to be maintained while the package is still
up. This
feature is called Package Maintenance mode and is available only for
modular
packages. For more information on using Package Maintenance mode,
refer the
whitepaper "Modular package support in Serviceguard for Linux
and ECM
Toolkits" located at http://docs.hp.com/en/ha.html
MONITOR_INTERVAL: The time interval in seconds between the
checks to
ensure that the DB2 database is running.
Default value is 30 seconds.
TIME_OUT: The amount of time, in seconds, to wait for
the DB2
shutdown to complete before killing
the DB2
processes defined in
MONITOR_PROCESSES. The
TIME_OUT variable is used to protect
against a
worst-case scenario where a hung database
prevents
the package halt script from completing,
thereby
preventing the standby node from starting
the
database. The value of TIME_OUT must
be less
than the HALT_SCRIPT_TIMEOUT value set
in the
package configuration file. This variable
has no
effect on the package failover times.
- Main Script (hadb2.sh)
This script contains a list of internally used variables and
functions
that support starting and stopping of a DB2 database instance. This
script
will be called by toolkit.sh to perform the following:
- On package startup, it starts the DB2 instance and monitor
process.
- On package halt, it stops the DB2 instance and monitor process.
- Monitor Script (hadb2.mon)