HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014

/dev/vg0_payroll/lvol1 (the logical volume)
/dev/vg0_payroll/lvol1 (the filesystem) mounted at /mnt/payroll
2. Test the set up to ensure that DB2 can be properly brought up. Tert st DB2 to ensure that it
can be properly started by executing the script toolkit.sh.
For example:
cd /tmp/db2
cp /opt/cmcluster/toolkit/db2/* .
Edit the DB2 toolkit configuration file hadb2.conf
./toolkit.sh start
After waiting for a few minutes, check for the several existence of DB2 processes which are
identified by "db2" , ps -ef | grep db2. Bring the database down, unmount, and deactivate
the volume group.
./toolkit.sh stop
umount /mnt/payroll
vgchange -a n /dev/vg0_payroll
Repeat this step on all other clustered nodes that must be configured to run the package and
ensure that DB2 can be brought up and down successfully.
The following section describes the methods for creating Serviceguard package using the
modular and legacy method. For more information on creating Serviceguard package using
modular method, see white paper Modular package support in Serviceguard for Linux and
ECM Toolkits available at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard
Enterprise Cluster Master Toolkit.
Creating Serviceguard package using Modular method
Create the Serviceguard package using Modular method.
To create Serviceguard package using Modular method, follow the below steps:
1. Create a directory for the package:
#mkdir /etc/cmcluster/pkg/db2_pkg/
2. Copy the toolkit template and script files from db2 directory:
#cd /etc/cmcluster/pkg/db2_pkg/
#cp /opt/cmcluster/toolkit/db2/* ./
3. Create a configuration file (pkg.conf).
#cmmakepkg -m ecmt/db2/db2 pkg.conf
4. Edit the package configuration file.
NOTE: DB2 toolkit configuration parameters in the package configuration file are prefixed
by ecmt/db2/db2 when used in Serviceguard A.11.19.00 or later. For example,
/etc/cmcluster/pkg/db2_pkg/pkg.conf
The configuration file must be edited as indicated by the comments in that file. The package
name must be unique within the cluster. For clarity, use the name of the database instance to
name the package. For example,
PACKAGE_NAME db2_payroll
List the names of the clustered nodes that must be configured to run the package, using the
NODE_NAME parameter.
NODE_NAME node1
NODE_NAME node2
Set the script_log_file variable. For example,
script_log_file /etc/cmcluster/pkg/<pkg_dir>/log
DB2 Package configuration example 81