Changes that affect all of the partitions in a HALDB database

Certain characteristics of HALDB partitions are shared by all of the partitions in a HALDB database.

Before you can change these characteristics, you must take all of the partitions in the HALDB database offline by issuing either the type-1 command /DBRECOVERY DB HALDB_master_name or the type-2 command UPDATE DB NAME(HALDB_master_name) STOP(ACCESS).

You can change the following characteristics of HALDB partitions only after you take offline all of the partitions the HALDB database:

DBD definition
A HALDB partition selection exit routine
Share level
Nonrecoverable attribute status
Maximum size of OSAM data sets for PHDAM and PHIDAM databases

Note: In addition to taking the partitions in the HALDB database offline, some of the changes listed above require you to unload all of the partitions, make the applicable change, reload the partitions, and then restore access to the partitions.

For example, suppose a HALDB database has an existing HALDB partition selection exit routine that needs to be replaced with a HALDB partition selection exit routine that selects partitions based on a new algorithm. This change requires the entire HALDB database to be offline because partition selection exit routines can affect the placement of records in every partition in the database. After taking the database offline, you must unload the database, make your changes to the exit routine, reload the database, and then restore access to the database.