2.32 pdfgt (Terminate transaction forcibly)

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Rules
(6) Notes

(1) Function

The pdfgt command terminates a transaction forcibly when a transaction branch that is part of a global transaction could not be terminated (due to a communication error, for example).

For example, transactions are not terminated in the following cases:

The pdfgt command can be used in such a case to terminate the transaction forcibly. The pdfgt command can also be used to terminate a transaction in which an error other than the above has occurred.

The pdfgt command terminates forcibly a transaction for which transaction status 1 is FORGETTING and transaction status 3 is w, as displayed by the pdls command (-d trn specified).

(2) Executor

HiRDB administrator

(3) Format

(a) HiRDB single server configuration

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

(b) HiRDB parallel server configuration

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

(4) Options

(a) {-x host-name| -u unit-identifier}

Specifies the name of the host or the unit identifier of the unit where the transaction to be terminated forcibly is located.

-x host-name ~<identifier> ((1-32))
Specifies the name of the host where the transaction to be terminated forcibly is located.
-u unit-identifier ~<identifier> ((4 characters))
Specifies the unit identifier of the unit where the transaction to be terminated forcibly is located.
(b) -s server-name ~<identifier> ((1-8))

For a unit with multiple servers, specifies a server name in order to specify a particular server. When this option is omitted, all servers at the object host are subject to the pdfgt command.

(c) -A

Specifies that all transactions at the server specified by the -s option that are in synchronization wait status and FORGETTING status are to be terminated forcibly.

(d) -t transaction-identifier ~<identifier> ((16 characters))

Specifies the transaction identifier of a transaction in synchronization wait status and FORGETTING status that is to be terminated forcibly.

(5) Rules

  1. The pdfgt command can be executed only while HiRDB is active.
  2. The pdfgt command must be executed at each server machine. However, it is not necessary to execute the command at a server machine of a utility special unit.

(6) Notes

  1. The results of the pdfgt command can be checked by the pdls command (with -d trn), by the return code of the pdfgt command, or by any error messages. Return code 0 for the pdfgt command indicates normal termination, and return code 1 indicates abnormal termination (such as an invalid option or rsh error).
  2. Forced termination 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 FORGETTING and transaction status 3 is w. In such a case, complete the transaction automatically. For details about how to complete a transaction that is in uncompleted status for transaction determination, see Forcing determination of uncompleted transactions in the HiRDB Version 9 System Operation Guide.
  3. If an uncompleted transaction resulting from a request from a client product that is currently stopped is forcibly terminated, that transaction might not be synchronized between HiRDB and the client product the next time that client product is started.