pdstop (Terminate HiRDB system, unit, or server)

Function

The pdstop command terminates a HiRDB system, unit, or server.

Executor

HiRDB administrator

Format

HiRDB/Single Server

pdstop [-d]

HiRDB/Parallel Server

 pdstop [{-x host-name|-u unit-identifier|-s server-name

            |-u unit-identifier -s server-name}] [-d]

pdstop -P[-d]

HiRDB/Single Server

pdstop -f[{-d|-q}]

HiRDB/Parallel Server

 pdstop {-f [{-x host-name|-u unit-identifier|-s server-name

                |-u unit-identifier -s server-name}[-d]]

          |-z[{-d|-q|-c|-s server-name}]}

Options

Specifies that the termination is to be by planned termination.

Difference between planned termination and normal termination is as follows:

Connected to HiRDBTransactionNormal terminationPlanned termination
NoNoYY
YesNN
YesNoNY
YesNN
Legend:
Y: Can be executed.
N: Cannot be executed.

Specifies that the termination is to be by forced termination. When this option is omitted, normal termination is executed.

Specifies the unit or server that is to be terminated. When this option is omitted, the HiRDB system is terminated.

-x host-name[Figure]<identifier> ((1-32))
When a unit is to be terminated, specifies the name of the host containing the unit. The host containing the system manager cannot be specified.
When the standby-less system switchover (effects distributed) facility is used, the command terminates the host and guest BESs on the specified host's unit. If the terminated server was the running system, it is released from acceptable status when viewed from another unit in the HA group.
-u unit-identifier[Figure]<identifier> ((4 characters))
When a unit is to be terminated, specifies the identifier of the unit. The unit identifier of the unit in which the system manager is located cannot be specified.
When the standby-less system switchover (effects distributed) facility is used, the command terminates the host and guest BESs on the specified unit. If the terminated server was the running system, it is released from acceptable status when viewed from another unit in the HA group.
-s server-name[Figure]<identifier> ((1-8))
When a server is to be terminated, specifies the name of the server.
When the standby-less system switchover (effects distributed) facility is used:
When the -u option is omitted, the command terminates the specified servers on all active units in the HA group.
When the -u option is specified, the command terminates the specified server on that unit. If the terminated server was the running system, it is released from acceptable status as viewed from other units in the HA group.
For details about the standby-less system switchover (effects distributed) facility, see the HiRDB Version 8 System Operation Guide.

Specifies that a unit other than the system manager is to be directly logged into and terminated forcibly; this option is specified when the system manager in a HiRDB/Parallel Server terminates abnormally and cannot be restarted.

If the pdstop command with the -z option specified is executed by mistake during HiRDB system startup or normal termination, the unit may terminate abnormally or the command may not be executed.

Specifies that a dump of shared memory is to be output at the time of termination. If the -s option is specified, this option is ignored. The shared memory dump is output to $PDDIR/spool/pdshmdump/shmdump.

If the system switchover facility is used, this option specifies that the specified system is to be terminated forcibly. You can specify this option if use is specified in the pd_ha operand, and the pd_ha_unit operand is also specified in the system definitions.

When the standby-less system switchover (1:1) facility is being used, specifies that the alternate system is to be terminated forcibly. Specify this option in the following cases:

To execute the pdstop -q -c command, directly log onto the host of the alternate system that is to be terminated forcibly (host specified in -x of the pdunit operand in the system definition).

When Real Time SAN Replication based on the log-only synchronous method is used, specifies that HiRDB is to be terminated at the log application site.

Rules
  1. The pdstop -l command can be executed at the log application site only. If the command is executed at the transaction execution site, an error results.
  2. The pdstop -l command results in an error if it is executed while there are any inactive units.

Rules

  1. The pdstop command can be executed only while HiRDB is active.
  2. The pdstop command must be executed on the server machine that contains the single server or utility special unit or the server machine where the system manager is located.
  3. Once the HiRDB system has been started by the pdstart command with the -r option specified, it cannot be terminated in units by specifying the -x option. In this case, either all options must be omitted or the -f option must be specified to terminate the HiRDB system.
  4. If the HiRDB system was started by the pdstart command with the -i option specified and the database initialization utility has been terminated, the -x option can be specified to terminate each unit of the HiRDB system. If the database initialization utility has not been terminated, the HiRDB system cannot be terminated in units by specifying the -x option. In this case, the -f option must be specified to terminate the HiRDB system.
  5. When the -z option is specified, the specified unit is stopped forcibly and any other options that are specified are ignored.
  6. When HiRDB is being terminated by the pdstop or pdstop -P command, pdstop -f -x host-name or pdstop -f -u unit-identifier cannot be used to execute forced termination.
  7. While the pdrplstart or pdrplstop command is executing, do not execute the pdstop command (except when the -f or -z option is specified).
  8. While a utility is executing, the pdstop command cannot terminate a system or unit normally. You can use the pdstop command to execute planned or forced termination.

Notes

  1. The following are the pdstop command's return codes:
    0: Normal termination
    4: Abnormal termination (communication timeout during planned termination)
    8: Abnormal termination (invalid option)
  2. The result of the pdstop command can be checked by the pdls command (with -d svr specified).
  3. Executing the pdstop command (with -f specified) during HiRDB startup or termination processing or during transaction processing may result in abnormal termination of the unit.
  4. If the pdstop command is entered with the -z option specified at a unit other than the system manager during normal operation of the system manager, that unit will be terminated abnormally.
  5. If HiRDB is linked to an OLTP system, OLTP must be terminated before HiRDB is terminated; otherwise, normal or planned termination of OLTP may fail because OLTP cannot process transactions.
  6. If planned termination does not end 15 minutes after the execution of the pdstop -P command because either a utility or a transaction was being executed, a KFPS05072-W message appears, indicating that the planned termination process is taking time. The planned termination process continues after the message.
  7. If you have specified the pd_log_auto_unload_path operand in the system definitions and executed the pdstop command while the automatic log unloading facility is running, you cannot terminate HiRDB until all the system log files have been unloaded. If you want to terminate HiRDB immediately, terminate the automatic log unloading facility using the pdlogatul -t command before executing the pdstop command.
  8. While updatable online reorganization is underway, you cannot specify the pdstop command (normal termination). If executed, the command results in an error. To terminate HiRDB while updatable online reorganization is underway, use the pdstop command for planned or forced termination (pdstop -P or pdstop -f).
  9. When you are using Real Time SAN Replication based on the log-only synchronous method, you can use the pdstop -l or pdstop -f command to terminate HiRDB at the log application site.