To start HiRDB at a unit, use the commands listed in the following table.

Table 1-5 Startup procedures for a unit

Startup mode	Execution command	Description of the startup mode	Previous termination mode
Normal startup	pdstart -u pdstart -x	This startup mode is used to restart a unit after it terminated normally during HiRDB operation. Information that was in effect during the previous session is not inherited. However, the following types of information are inherited: Status of replica RDAREAs Error shutdown status of RDAREAs	Normal termination
Restart#1		The restart mode is used (automatically) when the previous termination mode was one of those listed to the right. In this mode, the information that was in effect during the previous session is inherited. For details about the information inherited during a restart, see 20.1.5 Information inherited during a HiRDB restart.	Forced termination Abnormal termination
Forced startup#2	pdstart -u dbdestroy pdstart -x dbdestroy	Do not use this mode unless it is absolutely necessary. This mode starts the unit forcibly without restoring the database.	--

Legend:

--: Not applicable

#1: Read 1.7.2 Notes on planned termination, forced termination, and abnormal termination before restarting.

#2: Read 1.6.2 Notes on forced startup of HiRDB (or a unit) before forced startup is executed.

To terminate HiRDB at a unit, use the commands listed in the following table.

Table 1-6 Termination procedures for a unit

Termination mode	Input command	Description of the termination mode
Normal termination	pdstop -u pdstop -x	This mode prohibits any more CONNECT requests to this unit, disconnects all UAPs currently connected to the unit, then terminates the unit. If the unit cannot be terminated, even by executing the pdstop -u or pdstop -x command, because a utility is still running, the KFPS05070-E error message is output. The pdstop -u or pdstop -x command terminates with return code 8.
Forced termination#1	pdstop -f -u pdstop -f -x	This mode terminates the unit immediately without waiting for completion of current transactions. Current transaction become subject to rollback#2 during the subsequent restart.
Abnormal termination	--	This is the mode in which the unit is terminated because of an error. The unit is terminated immediately without waiting for completion of current transactions. Current transactions become subject to rollback#2 during the subsequent restart.

Legend:

--: Not applicable

#1: Read 1.7.2 Notes on planned termination, forced termination, and abnormal termination before restarting.

#2: 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.

To start and terminate a unit:

1. Enter the pdstart command to start and run HiRDB:
   pdstart
   
2. Because an error occurred in the unit, enter the pdstop -u command to terminate the unit normally (if the unit did not terminate abnormally):
   pdstop -u unit-identifier
   
3. After the error has been corrected, enter the pdstart -u command to restart the unit:
   pdstart -u unit-identifier