(a) servmax operand

You can specify this operand when the version of HA Monitor is 01-08 or later.

For servers that are switched using HA Monitor, specify 16 or 64 as the maximum number of servers that can be started concurrently as running servers or standby servers on a single server machine.

16: Sets 16 as the maximum number of servers that can be started concurrently.

64: Sets 64 as the maximum number of servers that can be started concurrently.

Specify 64 when the number of servers, which are the units for switching on a single server machine, exceeds 16.

The number of servers to be switched using HA Monitor also includes products other than HiRDB that are to be switched. HiRDB computes the number of servers to be switched as follows:

• Total number of running system units and standby system units that are running on a single server machine and that are subject to standby system switchovers
• Total number of normal BES units and alternate BES units that are running on a single server machine and that are subject to standby-less system switchovers (1:1)
• Total number of host BESs and guest areas that are running on a single server machine and that are subject to standby-less system switchovers (effects distributed)

(b) multistandby operand

You can specify this operand when the version of HA Monitor is 01-08 or later.

This operand specifies whether to use the multi-standby function, which defines multiple standby systems for a single running system.

• use: Use the multi-standby function
• nouse: Do not use the multi-standby function

The following table provides specification guidelines for the multistandby operand.

Table 26-13 Specification guidelines for the multistandby operand

Environment of the system switchover facility	multistandby operand specification
IP addresses are not inherited.	When IP addresses are not inherited, a multi-standby configuration cannot be applied.
IP addresses are inherited.	Specify use if a multi-standby configuration is applied.

Note

When use is specified, you must use the standbypri operand of the servers definition statement to specify priorities for the standby systems.

(a) acttype operand

To operate a system in the monitor mode, specify monitor in this operand.

(b) name operand

Specify a command (shell) for starting HiRDB (or a unit for a HiRDB parallel server configuration) using an absolute path name. If the environment variables inherited from HA Monitor are not appropriate for use by the HiRDB start command, HiRDB will not function properly. Use a user command (shell) to change the execution environment, and then execute the following command:

• For a HiRDB single server configuration: $PDDIR/bin/pdstart
• For a HiRDB parallel server configuration: $PDDIR/bin/pdstart -q^#
  #: This command starts a unit in the HiRDB parallel server configuration when the system switchover facility is being used.
  

The following example shows how to create a user command (shell) when you are using a HiRDB single server configuration.

Example:

PDDIR=/HiRDB_S
PATH=/bin:/usr/bin:/usr/ucb:$PDDIR/bin
PDCONFPATH=$PDDIR/conf
SHLIB_PATH=$PDDIR/lib
export PATH PDDIR PDCONFPATH SHLIB_PATH
$PDDIR/bin/pdstart

(c) termcommand operand

In the following cases, specify a command (shell) for terminating HiRDB (or a unit for a HiRDB parallel server configuration) using an absolute path name:

• When you are performing grouped system switchovers
• When you are terminating^# HiRDB by executing only the monend command of HA Monitor, or when you are performing a planned system switchover of HiRDB by executing only the monswap command

#

This applies when forcible termination is used. For normal termination, use the pdstop command to terminate HiRDB, and then execute the monend command.

If the environment variables inherited from HA Monitor are not appropriate for use by the HiRDB termination command, HiRDB will not function properly. Use a user command (shell) to change the execution environment, and then execute the following command:

• For a HiRDB single server configuration: $PDDIR/bin/pdstop or $PDDIR/bin/pdstop -f -q
• For a HiRDB parallel server configuration: $PDDIR/bin/pdstop -z -q

The following example shows how to create a user command (shell) when using a HiRDB single server configuration:

Example:

PDDIR=/HiRDB_S
PATH=/bin:/usr/bin:/usr/ucb:$PDDIR/bin
PDCONFPATH=$PDDIR/conf
SHLIB_PATH=$PDDIR/lib
export PATH PDDIR PDCONFPATH SHLIB_PATH
$PDDIR/bin/pdstop

Reference note

• If you specify this operand and enter HA Monitor's monswap command during HiRDB termination processing, the pdstop command results in an error (pdstop was entered while HiRDB was stopping). Although an error message is output at this time, this is not a problem.
• Even if you define a command (in the pd_ha_restart_failure operand) that is to be executed when restart fails, the pdstop command results in an error similar to the above case.

(d) alias operand

Specify an identifying name that is unique within the system to which HA Monitor is applied. You must specify the same identifying name in the primary and secondary systems.

For the standby-less system switchover facility, we recommend that you specify the unit identifier.

(e) disk operand

Specify the name of the disk area (volume group and partition) in which a HiRDB file system area was created. For details, see the manual High-Availability System Monitoring Facility.

(f) lan_updown operand

If IP addresses are inherited:

To turn the power to the network on or off, you can specify the IP address to be inherited in the .up file or the server identifier's .down file as the alias operand value. To do this, you must also specify use in the lan_updown operand.

If IP addresses are not inherited:

Before starting the running system and standby system HiRDB (or unit), you can activate the IP addresses specified in the -x and -c options of the pdunit operand. Do not specify an IP address specified in the -x or -c option of the pdunit operand in the alias operand value's .up or .down file for HA Monitor. If IP addresses for client connections are to be inherited, specify these IP addresses. If there are no IP addresses to be inherited, such as IP addresses for client connections, specify nouse in the lan_updown operand of the server definition file of HA Monitor, or delete the alias operand value's .up and .down files.

(g) group operand

Specify this operand in order to perform grouped system switchovers. However, you do not need to specify this operand if the only server to be switched is HiRDB. Specify a server group name in this operand. The following examples provide guidelines for specifying server group names:

• If you are using OpenTP1 and performing grouped system switchovers, specify the same value as the definition file that set up the environment for the specified server in OpenTP1 of the same system.
• If you are using HiRDB Datareplicator and performing grouped system switchovers, specify the same value as the definition file that set up the environment for the specified server in HiRDB Datareplicator.

(h) initial operand

Specify online for the primary system and standby for the secondary system.

(i) standbypri operand

You can specify this operand if the version of HA Monitor that you are using is 01-08 or later.

You can use this operand to specify standby system priorities when you use the multi-standby facility of HA Monitor (when use is specified in the multistandby operand in the sysdef definition file) to operate a system in a multi-standby configuration.