/etc/cmcluster/pkg/db2_pkg/toolkit.sh stop

test_return 52

}

The Serviceguard package configuration file (pkg.conf).

The package configuration file is created with cmmakepkg -p, and should be put in the following location:

/etc/cmcluster/pkg/db2_pkg/

For example:

/etc/cmcluster/pkg/db2_pkg/pkg.conf

The configuration file should be edited as indicated by the comments in that file. The package name needs to be unique within the cluster. For clarity, use the name of the database instance to name the package.

PACKAGE_NAME db2_payroll

For example:

PACKAGE_NAMEdb2_payroll

List the names of the clustered nodes to be configured to run the package, using the NODE_NAME parameter:

NODE_NAME

node1

NODE_NAME

node2

The service name must match the service name used in the package control script. The service name can include the DB2 instance name (that is, $DB2_INSTANCE). In the following example, since there is only one service for this package, the ${DB2_INSTANCE} (that is,payroll_inst) is assigned to the SERVICE_NAME parameter. For example,

SERVICE_NAME

payroll_inst_service

SERVICE_FAIL_FAST_ENABLED

NO

SERVICE_HALT_TIMEOUT

300

The run and halt scripts are (typically) identified as the control script, as follows:

RUN_SCRIPT /etc/cmcluster/pkg/db2_pkg/pkg.cntl

HALT_SCRIPT /etc/cmcluster/pkg/db2_pkg/pkg.cntl

The DB2 Configuration file, in the package directory, modify the hadb2.conf configuration file for this DB2 instance. Edit the hadb2.conf as indicated by the comments in that script. For example,

INSTANCE_NAME=db2_payroll_inst

PARTITION_NUMBER[0]=0

PARTITION_NUMBER[1]=1

MONITOR_PROCESSES[0]=db2sysc

MONITOR_PROCESSES[1]=db2acd

MAINTENANCE_FLAG=YES

MONITOR_INTERVAL=30

TIME_OUT=30

After setting up the Serviceguard environment, each clustered DB2 instance should have the following files in the related package directory. For example, the DB2 package, located at /etc/cmcluster/pkg/db2_pkg, would contain the following files:

84 Using the DB2 database Toolkit in a Serviceguard Cluster in HP-UX