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

or for use with Asynchronous disk access and file systems:
/dev/vg01_payroll/lvol1 #Logical volume DB2 data
/dev/vg02_payroll/lvol1 #Logical volume DB2 data
/dev/vg03_payroll/lvol2 #Logical volume DB2 data
D. Setting Up the Toolkit
- Toolkit Overview
After installing this toolkit, three scripts and this README file
will be
present in the /opt/cmcluster/toolkit/db2/ directory. Two more scripts
and one Attribute Definition File will be present which will be used
only by
modular packages. These scripts will be in the
/etc/cmcluster/scripts/ecmt/db2/
directory. The Attribute Definition file for modular packages
will be
preter, include the identity of the db instance in their namesent in
the
/etc/cmcluster/modules/ecmt/db2/ directory.
For legacy packages, there will be one user configuration script
(hadb2.conf)
and three functional scripts (toolkit.sh, hadb2.sh and hadb2.mon)
which work
with each other to integrate DB2 with the Serviceguard package
control
scripts.
For modular packages,there is an Attribute Definition File(ADF), a
Toolkit
Module Script (tkit_module.sh) and a Toolkit Configuration File
Generator
Script (tkit_gen.sh) which work with the three scripts mentioned
above for
legacy packages to integrate DB2 with the Serviceguard Master Control
Script.
These scripts are:
- hadb2.conf (user configuration file)
This script contains a list of pre-defined variables that the
user must
customize for use with a particular database instance. This is a
configuration
file which is read by the toolkit script, hadb2.sh. The following
variables
are contained in hadb2.conf:
INSTANCE_NAME: The DB2 instance name.