The pdtrnqing command starts or releases transaction queuing.

In a HiRDB parallel server configuration, you can apply transaction queuing (execute the pdtrnqing command) only to units that satisfy either of the following conditions:

1. Unit consisting of front-end servers only.
2. Unit consisting of a system manager and front-end servers only.

Transaction queuing (execution of the pdtrnqing command) is not applicable to a unit that does not satisfy either of these conditions.

In this manual, a unit that satisfies either of these conditions is called a front-end server unit.

The pdtrnqing command is used to queue new transactions before planned system switchover is performed by the standby system switchover facility. The following discusses for each system configuration the HiRDB processing that occurs when the pdtrnqing command is executed.

• In a HiRDB single server configuration
  When the pdtrnqing command is executed, queuing of new transactions begins and the new transactions will be placed in wait status (except for a transaction that is being executed). Because the new transactions will be queued, no transaction error will occur when the planned system switchover is performed.
  
• In a HiRDB parallel server configuration
  When the pdtrnqing command is executed, queuing of new transactions begins for the target unit (front-end server unit) and the new transactions will be placed in wait status (except for a transaction that is being executed). Because new transactions will be queued for the front-end server unit, no transaction error will occur when the planned system switchover is performed on the front-end server unit.
  

  Note

  To execute planned system switchover, you must have specified YES in the PDAUTORECONNECT operand in the client environment definition in advance and must have applied the automatic reconnect facility. Otherwise, a UAP that attempts to connect to HiRDB during the planned system switchover might result in a CONNECT error.

HiRDB administrator

pdtrnqing [-d|-t wait-time]

(a) -d

Specifies that transaction queuing is to be released.

(b) -t wait-time ~<unsigned integer>((1~3600))<<180>> (seconds)

Specifies the amount of time (in seconds) that the pdtrnqing command is to wait for completion of an executing transaction (for a HiRDB parallel server configuration, the wait is for a transaction executing on the front-end server unit). If an executing transaction is not completed within the specified number of seconds, the pdtrnqing command cancels transaction queuing and terminates itself with an error.

1. In a HiRDB parallel server configuration, you must execute the pdtrnqing command at the unit where the transaction queuing instruction is to be applied (starting or releasing). Transaction queuing is applied to the unit when the pdtrnqing command executes.
2. The pdtrnqing command cannot be executed at an inactive unit.
3. In the following cases, the pdtrnqing command terminates normally and the transaction queuing application status remains unchanged:
   
   • While the transaction queuing instruction was being applied, an attempt was made to restart transaction queuing by executing another pdtrnqing command.
   • Transaction queuing was not being performed, but an attempt was made to release transaction queuing by executing the pdtrnqing -d command.

1. Do not execute the pdtrnqing command while any other command is executing. If the pdtrnqing command is executed while another command is executing, the other command might terminate with an error.
2. If you execute the pdtrnqing command in the following cases, the pdtrnqing command will terminate with an error:
   
   • The current HiRDB is being updated to the HiRDB update version (the pdprgrenew command is being executed)
   • The system reconfiguration command (pdchgconf) is executing
3. If you attempt to start transaction queuing with the pdtrnqing command in the following cases, the pdtrnqing command terminates with an error:
   
   • A utility is executing
   • Updatable online reorganization is underway
   • Start processing for transaction queuing is underway
4. If you perform any of the operations listed below while the pdtrnqing command is waiting for completion of an executing transaction, the other operation's command processing takes precedence, in which case the pdtrnqing command is canceled and terminates with an error:
   
   • Normal or planned termination of HiRDB (pdstop command)
   • Forced termination of HiRDB (pdstop command)^#
   • Updating to the HiRDB update version (pdprgrenew command)
   • Executing the system reconfiguration command (pdchgconf command)
   • Releasing transaction queuing (pdtrnqing -d command)
   #: If you terminate HiRDB forcibly, the pdtrnqing command is also terminated forcibly (killed).
   
5. Transaction queuing is released automatically when any of the operations listed below is performed:
   
   • Restarting the unit for which transaction queuing is being performed (including when system switchover has occurred on the unit)
   • Terminating the system, unit, or server (pdstop command)^{#1, #2}
   • Updating to the HiRDB update version (pdprgrenew command)
   • Executing the system reconfiguration command (pdchgconf command)

   #1

   Transaction queuing is released if the unit for which transaction queuing is being performed or a server in that unit is terminated.

   #2

   Transaction queuing might also be released when the pdstop command terminates with an error.

6. The pdtrnqing command queues UAP transactions other than the following transactions:
   
   • Transactions that execute definition SQL statements
   • Transactions that use a holdable cursor
   • Transactions that execute the ASSIGN LIST statement
   • Transactions that execute the LOCK statement with UNTIL DISCONNECT specified
   • Transactions using the X/Open XA interface
   • Transactions for commands and utilities

The following are the pdtrnqing command's return codes:

0: Normal termination

4: Warning

8: Error termination

12: Error termination

Return codes 8 and 12 indicate that the command was unable to start or release transaction queuing. In this case, a message is output to the syslogfile and to the standard error output.

The command terminates with return code 8 if the executing environment was invalid or an erroneous operation was performed; in all other cases, the command terminates with return code 12.