The planned system switchover procedure is as follows.

Procedure

1. Use the pdls -d ha command or the corresponding cluster software command to confirm the following:
   The unit subject to the planned system switchover is active.
   The planned system switchover target unit is in standby status.
   
2. Execute the pdtrnqing command at the source unit and start transaction queuing.
   During this step, confirm that the pdtrnqing command terminated normally with a return code of 0. If the return code is 0, transaction queuing has started normally. If the return code is 8 or 12, transaction queuing has not started. In this case, eliminate the cause of the problem, and then re-execute the pdtrnqing command.
   
3. Use a cluster software command (the monswap command for HA Monitor) to execute the planned system switchover.
4. Use the pdls -d ha command or the corresponding cluster software command to confirm that the switchover target unit is active.

When the planned system switchover is complete, transaction queuing is automatically canceled, and the transactions that have been queued are executed. This method can only be used for planned system switchovers when the automatic reconnect facility is applied. Therefore, check whether this facility is applied. For details about the automatic reconnect facility, see the HiRDB Version 9 UAP Development Guide.

When this method is used for a planned system switchover, UAP transactions are queued and placed in waiting status after the pdtrnqing command is executed until the planned system switchover is complete. This increases the response time. Therefore, check whether the following settings are appropriate:

• Client maximum wait time specified in the PDCWAITTIME operand of the client environment definition
• HiRDB client maximum wait time when connecting to the server, specified in the PDCONNECTWAITTIME operand of the client environment definition

When the time specified by these operands elapses, UAP execution results in an error.

The planned system switchover procedure is as follows.

Procedure

1. Use the pdstop command to terminate the running system HiRDB (unit or server). Perform this step only when a product other than HA Monitor is used as the cluster software.
   If you specify the pdstop command in the termcommand operand of Hitachi HA Toolkit Extension, you do not have to execute the pdstop command at this time, because Hitachi HA Toolkit Extension executes it as an extension of the command in step 2.
   
2. Use a cluster software command (the monswap command for HA Monitor) to perform the planned system switchover. For details about planned system switchovers, see the documentation for the applicable cluster software product.
3. The HiRDB (or unit) that became the standby system must be placed in standby status. Execute the pdstart command (the pdstart -q command for a HiRDB parallel server configuration) on the standby system HiRDB.