After an aborted session you start the DBH in the usual way. If required you can also start the DBH on a different system from that of the aborted session. A switchover of the server architecture (/390 server <---> x86 server) is also possible here.
However, when passing the DBH start parameters, note the following:
The configuration name and DBH name of the aborted and restarted sessions must be the same (see the DBH options “CONFIGURATION-NAME” and “DBH-NAME”). An external restart is only carried out if you start a DBH with the same configuration name and DBH name as the aborted session. Only in this case can the DBH evaluate the restart information in the corresponding TA-LOG files and WA-LOG file.
If you do not want to use the default values for one or more parameters, you have to enter the DBH option MEDIA-CATALOG (see "MEDIA-CATALOG").
You must enter the DBH options CURSOR-BUFFER, SYSTEM-DATA-BUFFER and USER-DATA-BUFFER (see "CURSOR-BUFFER"ff) if you wish to use a value other than the default value for one or more of these options.
In the event of an error (see "Requirements for starting") the BS2000 system administrator must enlarge the ID’s virtual address space. If this is not possible, you can attempt to reduce the storage requirements using restrictions in some DBH options (see the higher-order DBH option STORAGE-SIZE, "STORAGE-SIZE").The DBH adopts the other DBH start parameters from the WA-LOG file. Any additional start parameters you enter are ignored. The LOGICAL-ROLLBACK = IMMEDIATELY / DELAYED parameter of the RESTART-CONTROL administration statement is an exception to this because. Here you can also change its value subsequently.
If one of the relevant databases or a space is not available, you receive a message to this effect. The DBH expects one of the following responses:
R I H | to attempt to open it again to skip the database or space and resume processing to abort the restart |
Even when databases or spaces cannot be made available to the DBH, it still tries to complete the restart successfully. These databases or spaces can then be repaired by means of the RECOVER utility statement (see the “ SQL Reference Manual Part 2: Utilities”).
During the restart, the DBH does not process any requests; administration statements or commands cannot be executed during this phase.
Once the restart has been successfully completed, the databases remain open and application programs can again work with them.