1.1.1 Startup modes

HiRDB employs the concept of the startup modes listed in Table 1-1. The pdstart command's options depend on the startup mode.

Table 1-1 HiRDB startup modes

Startup modeExecution commandDescription of the startup modePrevious termination mode
Normal startuppdstartThis is the usual startup mode. In this mode, information that was in effect during the previous session is not inherited. However, the error shutdown status of RDAREAs is inherited.Normal termination
Restart1This is the mode that 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.
  • Planned termination
  • Forced termination
  • Abnormal termination
Forced startup2pdstart dbdestroyThis mode should not be used unless it is absolutely necessary. When HiRDB cannot be restarted, this mode is used to start HiRDB forcibly.[Figure]
[Figure]3pdstart -iThis mode should not be used unless it is absolutely necessary; it is used when a database is being reinitialized.
pdstart -rThis mode should not be used unless it is absolutely necessary; it is used in the event of an error in the master directory RDAREA.
pdstart -aThis mode should not be used unless it is absolutely necessary; it is used when the front-end server is in SUSPEND status.

1 Section 1.7.2 Notes on planned termination, forced termination, and abnormal termination should be read before HiRDB is restarted.

2 Section 1.6.2 Notes on forced startup of HiRDB (or a unit) should be read before forced startup is executed.

3 For details on using these startup methods, see 1.3 Special startup procedures.