9.8 mondeact (terminates a server in the wait state)

Format

mondeact server-alias-name

Users who can execute the command

Superuser

Description

The mondeact command terminates the following servers:

• Standby server in the active server start wait state

  If a server defined as a standby server in the server environment definition cannot check the status of the active system during startup processing due to an error (such as a communication error), it is placed in the wait state until the active server in the active system has started. This command forcibly terminates such a standby server that is in this status.

• Active server in the restart wait state

  An active server for which restart or manual is specified in the switchtype operand in the server environment definition is placed in the restart wait state without being switched over in the event of a server failure. This command forcibly terminates such an active server that is in this wait state. When an active server in the restart wait state is terminated by execution of the mondeact command, the corresponding standby server is also terminated automatically.

• Active server in the hot-standby wait state

  If host reset fails, the standby server in the standby system is switched in as the active server but then is placed in the hot-standby wait state. This command forcibly terminates such an active server that is in this wait state.

  If the multi-standby function is used and the active server in the hot-standby wait state is terminated by executing the mondeact command, the corresponding standby servers on all hosts are also terminated automatically.

• Active server in the start retry state

  If an active server for which retry is specified in the switch_error operand in the server environment definition fails to start at the destination during hot standby processing, it is placed in the start retry state. The mondeact command forcibly releases the active server from this status.

  The mondeact command can release an active server during the following time periods:

  • Server in the server mode

    From the time the KAMN310-I message is issued to the time the KAMN251-I or KAMN254-I message is issued

  • Server in the monitor mode

    From the time the KAMN310-I message is issued to the time the KAMN252-I message is issued

Options

• server-alias-name

  Specifies the alias name of the server that is to be terminated.

Return codes

Notes

• You can execute the mondeact command only on servers in the following statuses:

  • Standby server in the active server start wait state

  • Active server in the restart wait state

  • Active server in the hot-standby wait state

  • Active server in the start retry state

• The mondeact command cannot be executed on a server in the resource server start wait state.

• If a server is waiting for startup of a resource server and the resource server is also in the start wait state, you can terminate both the server and the resource server by executing the mondeact command on the resource server. The KAMN377-E message will be issued in such a case, but there is no problem.

• To terminate a server while the server and the resource server are both in the hot-standby wait state, execute the mondeact command on the server. The KAMN377-E message will be issued in such a case, but there is no problem.

• The return code is also set to 0 when any of the following messages is issued while type2 is specified in the exitcode operand in the HA Monitor environment settings:

  KAMN322-E, KAMN337-E, KAMN339-E, KAMN465-E

• The wait-state server does not terminate at the same time that the mondeact command's return code is received.