When a HiRDB/Parallel Server is being used, each unit can be started and terminated independently.
HiRDB can be started at a unit with the commands listed in Table 1-5.
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. | Normal termination |
Restart1 | 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. | Forced termination Abnormal termination | |
Forced startup2 | pdstart -u dbdestroy pdstart -x dbdestroy | This mode should not be used unless it is absolutely necessary. This mode starts the unit forcibly without restoring the database. | ![]() |
1 Section 1.7.2 Notes on planned termination, forced termination, and abnormal termination should be read before restarting.
2 Section 1.6.2 Notes on forced startup of HiRDB (or a unit) should be read before forced startup is executed.
HiRDB can be terminated at a unit with the commands listed in Table 1-6.
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 termination1 | pdstop -f -u pdstop -f -x | This mode terminates the unit immediately without waiting for completion of current transactions. Current transaction become subject to rollback2 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 rollback2 during the subsequent restart. |
1 Section 1.7.2 Notes on planned termination, forced termination, and abnormal termination should be read before restarting.
2 Current transactions become subject to rollback during a HiRDB restart except in the following cases:
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 19.2 Recovering a database to the point at which a backup was made.