pdcmt (Commit transactions)

Function

The pdcmt command forcibly commits transactions when none of the transactions that are part of a global transaction could be concluded (for example, because of a communications error). All the transactions in the global transaction must be committed, otherwise they will not be synchronized.

The pdcmt command is used to forcibly commit transactions that are shown in the status information displayed by the pdls -d trn command as being in READY status (Status 1) and p status (Status 2).

Executor

HiRDB administrator

Format

pdcmt {-x host-name | -u unit-identifier} [-s server-name]
     {-A | -t transaction-identifier}

Options

Specifies the identifier of the unit or the name of the host in which the transactions to be committed are located.

-x host-name[Figure]<identifier> ((1-32))
Specifies the name of the host in which the transactions to be committed are located.
-u unit-identifier[Figure]<identifier> ((4 characters))
Specifies the identifier of the unit in which the transactions to be committed are located.

Specifies the server name when the unit has multiple servers. If this option is omitted, all servers in the object host are subject to the pdcmt command.

Specifies that all transactions in the server specified by the -s option that are in READY status and recovery waiting status are to be committed.

Specifies that the transaction identifier of a transaction in READY status and recovery processing waiting status is to be committed.

Rules

  1. The pdcmt command can be executed only while HiRDB is active.
  2. Execute the pdcmt command at each server machine. Note that you cannot execute this command at the server machine on a utility special unit.

Notes

  1. The results of the pdcmt command can be checked on the basis of the return code from execution of the pdls command (with -d trn specified) or by checking for any error messages. Return code 0 for the pdcmt command indicates normal termination, and return code 1 indicates abnormal termination (such as an invalid option or rsh error).
  2. Forced commit may not be possible for a transaction that is connected to a recovery-unnecessary front-end server and executed, even if transaction status 1 is READY and transaction status 2 is p. In such a case, you must complete the transaction automatically; for details about how to complete a transaction that is in uncompleted status for transaction determination, see the manual HiRDB Version 8 System Operation Guide.