18.1.5 Information inherited during a HiRDB restart

Table 18-4 shows the information that is inherited during a HiRDB restart.

Table 18-4 Information inherited during a HiRDB restart

ClassificationInformation that is inherited
System filesSystem log filesSystem recovery information
Synchronization point dump filesTable recovery information
Status files
  1. Information used to determine the system startup mode:
    [Figure]Server configuration
  2. Status information about each system server:
    [Figure]Open/close status
    [Figure]Primary/standby (alternate) status
    [Figure]File shutdown status
    [Figure]Service group shutdown status
  3. RDAREA-related information
User data (database)RDAREAs
  • Open/close status
  • Shutdown status*
Operation commands (status changes made by the commands shown at the right are inherited)Database manipulation commands
  • pdclose (close RDAREA)
  • pdopen (open RDAREA)
  • pdhold (shut down RDAREA)*
  • pdrels (release RDAREA from shutdown status)
Commands for manipulating system log files or synchronization point dump files
  • pdlogadpf (allocate file)
  • pdlogchg (change file status)
  • pdlogcls (close file)
  • pdlogopen (open file)
  • pdlogswap (swap files)
  • pdlogunld (unload file)
Commands for manipulating status files
  • pdstscls (close file)
  • pdstsopen (open file)
  • pdstsswap (swap files)
Commands for output of audit trails
  • pdaudbegin command (begin collection of audit trail)
  • pdaudend command (end collection of audit trail)
Note
The following information is not inherited (these commands must be entered again after HiRDB is restarted):
  • pdstbegin (start collection of statistical information)
  • pdstend (terminate collection of statistical information)
* The following hold statuses are not inherited:
  • Referencing-permitted backup-hold (update WAIT mode)
  • Updatable backup-hold
  • Updatable backup-hold (WAIT mode)