41.2.1 Explanation of the specification format and options

Organization of this subsection

(1) Specification format
(2) Explanation of options

(1) Specification format

adbstop [{--wait {connection|transaction} [-t timeout-value] [--node]
         |--cancel [--node]
         |--force
         |--node}]

To Page Top

(2) Explanation of options

Specifies the HADB server termination method.

• --wait {connection|transaction} [-t timeout-value]

The command is to wait until all application programs have disconnected from the HADB server, all active transactions have completed, and all executing commands have terminated, and then the HADB server is to be terminated normally.

connection

Specifies that the command is to wait until all application programs have disconnected from the HADB server and all executing commands have completed, and then the HADB server is to be terminated.

Note that once the adbstop command with --wait connection specified is executed, the HADB server will no longer accept new connection establishment requests. The HADB server will still accept new transaction start requests.

transaction

Specifies that the command is to wait until all active transactions have completed, all executing commands have terminated, and all applications that are connected to the HADB server have disconnected, and then the HADB server is to be terminated.

Note that once the adbstop command with --wait transaction specified is executed, the HADB server will no longer accept new connection establishment requests or new transaction start requests.

-t timeout-value

~<integer>((1 to 86,400))<<3,600>>(seconds)

This option can be specified only when --wait connection or --wait transaction is specified.

Specifies the amount of time (in seconds) the command is to wait for disconnection of application programs, completion of transactions, and termination of commands. If the amount of time specified in this option expires (resulting in a timeout) while the adbstop --wait command is still executing, the HADB server is not terminated and it can resume accepting both new connection establishment requests and new transaction start requests.

• --cancel

The command is to cancel all active transactions and all executing commands, then disconnect all application programs from the HADB server, and then terminate the HADB server.

Note that once the adbstop command with --cancel specified is executed, the HADB server will no longer accept new connection establishment requests or new transaction start requests.

• --force

The command is to terminate the HADB server forcibly without waiting for active transactions to be completed or executing commands to be terminated. When the HADB server is terminated forcibly, transaction recovery processing will be performed the next time the HADB server is started.

Note that when the adbstop command with --force specified is executed, the KFAA91153-Q message is output. The KFAA91153-Q message asks you to confirm that you really want to terminate the HADB server forcibly. If you want to terminate the HADB server forcibly, enter Y. If anything other than Y is entered, adbstop command processing is canceled.

If the multi-node function is used:

If the adbstop command with --force specified is executed, only the HADB server on the node on which the command is executed is forcibly terminated. If the command is executed on the master node, one of the slave nodes is switched to the master node.

• --node

This option is related to the multi-node function. This option is specified when terminating an HADB server on a specific node. In the following cases, execute the adbstop command with the --node option specified.

Terminating the HADB server on a specific slave node

On the slave node on which you want to terminate the HADB server, execute the adbstop command with the --node option specified.
Switching over the master node (when SCSI reservation for shared disk is in use)

To switch over the master node when SCSI reservation for shared disk is used, execute the adbstop command with the --node option specified on the master node to terminate the master node's HADB server. For details about how to switch over the master node, see the topic Switching over the master node by using a command in the HADB Setup and Operation Guide.

Important

If host reset is being used rather than SCSI reservation for shared disk, do not execute the adbstop command with the --node option specified on the master node. If host reset is being used and the adbstop command with the --node option specified is accidentally executed on the master node, execute HA Monitor's monswap command to switch over the master node. For details, see Operations When Using the Multi-Node Function in the HADB Setup and Operation Guide: Normally terminating the HADB server on the master node only under Terminating an HADB server on a specific node under Terminating HADB servers in the multi-node configuration in Starting and terminating HADB servers in the multi-node configuration

Note: When the multi-node function is not being used, this option is ignored.

The system processing for when both the --node option and another option are specified is described in the table below.

Table 41‒1: System processing for when both the `--node` option and another option are specified
No.	Options specified with the `--node` option	System processing
1	None	If the `adbstop` command is executed on a slave node If an ongoing transaction exists on the node on which the `adbstop` command is executed, an error occurs (the `KFAA50021-E` message is output). If the `adbstop` command is executed on the master node An error occurs (the `KFAA50021-E` message is output) in the following cases. An ongoing transaction exists on the master node. A connection has been established with an HADB server in the multi-node configuration, but no transaction has been executed on that connection.
2	`--wait` `connection`	If the `adbstop` command is executed on a slave node Termination processing waits for the completion of the ongoing transaction on the node on which the `adbstop` command is executed. The termination processing begins when all transactions have been completed. In this case, start requests for new transactions are not accepted by that node. If the `adbstop` command is executed on the master node Termination processing waits for the completion of the ongoing transaction on the master node. If a connection established with an HADB server in the multi-node configuration has not been used to execute transactions, termination processing waits for the completion of that connection. The termination processing begins when all transactions and connections have been completed. In this case, the master node does not accept new transaction start requests or new connection establishment requests.
3	`--wait` `transaction`	If the `adbstop` command is executed on a slave node Termination processing waits for the completion of the ongoing transaction on the node on which the `adbstop` command is executed. The termination processing begins when all transactions have been completed. In this case, start requests for new transactions are not accepted by that node. If the `adbstop` command is executed on the master node Termination processing waits for the completion of the ongoing transaction on the master node. Even if a connection established with an HADB server in the multi-node configuration has not been used to execute transactions, the termination processing begins upon completion of the ongoing transaction on the master node. (The connection is terminated forcibly). In this case, the master node does not accept new transaction start requests or new connection establishment requests.
4	`--cancel`	If the `adbstop` command is executed on a slave node The ongoing transactions on the node on which the `adbstop` command is executed are canceled, and the connection that is executing that transaction is terminated. Next, the termination processing starts. In this case, start requests for new transactions are not accepted by that node. If the `adbstop` command is executed on the master node The ongoing transaction on the master node is canceled. Then, the connection used for executing that transaction is terminated. If a connection established with an HADB server in the multi-node configuration has not been used to execute transactions, that connection is terminated. The termination processing begins when all connections have been completed. In this case, the master node does not accept new transaction start requests or new connection establishment requests.

If no option is specified, the HADB server's termination mode is set to normal termination. If any application program is connected to the HADB server or a command is executing, the KFAA91152-E message will be output and an error will result (the HADB server cannot be terminated). If this happens, see the manual HADB Messages and take the appropriate action described for the KFAA91152-E message.

To Page Top