HiRDB employs the termination modes listed in the table below. The pdstop command's options depend on the termination mode.

Table 1-4 HiRDB termination modes

Termination mode	Input command	Description of the termination mode
Normal termination#1	pdstop	This is the normal termination mode. This mode prohibits CONNECT requests and terminates HiRDB once all user processes have terminated. However, if a utility is still running, the KFPS05074-E error message is output and HiRDB is not terminated. The pdstop command terminates with return code 8.
Planned termination#1, #2, #3	pdstop -P	This mode prohibits acceptance of any new transactions and terminates HiRDB after all transactions, including utilities, have terminated.
Forced termination	pdstop -f	This mode terminates HiRDB immediately without waiting for completion of current transactions. Current transactions become subject to rollback#4 during the subsequent HiRDB restart.
Abnormal termination	--	This is the mode in which HiRDB is terminated because of an error. HiRDB is terminated immediately without waiting for completion of current transactions. Current transactions become subject to rollback#4 during the subsequent HiRDB restart.

#1: If HiRDB is linked to an OLTP system, the OLTP system must be terminated before normal or planned termination of HiRDB is executed. Otherwise, an attempt to terminate HiRDB by normal or planned termination might fail, because transaction processing cannot be executed on the OLTP system.

#2: When planned termination of HiRDB is executed, the system resources held by the HiRDB server processes are released after all the active transactions are terminated in the single server or front-end server. It might take a minute or so for this release processing to be completed after all transactions at a unit have terminated.

#3: If planned termination of HiRDB has not been completed within 15 minutes of entering the pdstop -P command because a utility or transaction is still executing, the KFPS05072-W message is output and the pdstop -P command is terminated with return code 4. In such a case, planned termination processing is still in effect, and HiRDB will be terminated once the utility or transaction has terminated.

#4: Current transactions become subject to rollback during a HiRDB restart except in the following cases:

• The database load utility or database reorganization utility was executing in the no-log mode.
• The UAP was executing in the no-log mode.

In such a case, the HiRDB administrator must restore the RDAREAs from backup copies or re-execute the utility after HiRDB has been restarted. For details on how to restore RDAREAs, see 21.2 Recovering a database to the point at which a backup was made.