The following IMS commands can be issued against High Availability Large Databases (HALDBs). The commands are:
|When you enter one of these commands, the database |name can be an existing non-HALDB, a HALDB master, or a HALDB partition. A |command against a HALDB partition operates exactly like a command against |a non-HALDB with the exception of the /START DATABASE and the UPDATE DB START(ACCESS) command. A HALDB partition is not allocated during the command |unless it was previously authorized but not allocated, the OPEN |keyword was specified, or the partition has EEQEs. The partition is |allocated at first reference.
The HALDB partition reflects conditions such as STOPPED, LOCKED, or NOTOPEN. When a HALDB partition is stopped, it must be explicitly started again. Commands with the keyword ALL and commands against a HALDB master do not change the STOPPED and LOCKED indicators in each HALDB partition.
When the command target is a HALDB master, processing acts on all HALDB partitions. For example, if the IMS command is /DBR on the HALDB master, all of the HALDB partitions are closed, deallocated, and unauthorized. Only the HALDB master displays STOPPED (each HALDB partition does not display STOPPED unless it was itself stopped). If a /DBR command was issued against a HALDB master, the display output of a /DISPLAY DATABASE command shows the HALDB master (as STOPPED), but does not display the status of the partitions.
Each partition inherits the access limitations of its HALDB master. If the /DBD command is issued against a HALDB master, all of its partitions close. A subsequent reference to any of the partitions results in the partition opening for input, although the partition's access might be UPDATE or EXCLUSIVE. The DBRC authorization state reflects the limited access.