Restrictions for HALDB Online Reorganization
The following restrictions apply to HALDB Online Reorganization
The restrictions include:
- You can perform an online reorganization only for a HALDB that
is defined in the RECON data sets as capable of being reorganized
online. The OLRCAP parameter of the
INIT.DBcommand or theCHANGE.DBcommand defines a HALDB as being OLRCAP. - A HALDB that uses 8-GB OSAM data
sets cannot be reorganized online. To be reorganized online, the HALDB
must use 4-GB OSAM data sets. The OSAM8G and NOOSAM8G parameters of
the
INIT.DBcommand or theCHANGE.DBcommand defines the maximum data set capacity. OLRCAP and OSAM8G are mutually exclusive parameters and flags in the RECON data sets. - You cannot start an online reorganization for a partition if another IMS system already owns an online reorganization for that partition. This is the default behavior. To change the default behavior, specify the RELOLROWNER parameter in the DATABASE section of the DFSDFxxx member of the IMS.PROCLIB data set to instruct IMS systems that terminate during an online reorganization to release ownership of the reorganization. Another IMS system can then resume the reorganization. You can also use the OPTION(REL) parameter of the INITIATE OLREORG command to override the default behavior for a single, specific online reorganization.
- You cannot start an online reorganization of any partition that has a status of ALTER IN PROGRESS.
- Image copy for a partition is not allowed if the partition is in the cursor-active status. This restriction applies even if the online reorganization terminated before the cursor-active status has been reset and the online reorganization for the partition is not owned by any IMS.
- Image copy for a partition is not allowed if the partition has an ALTER IN PROGRESS status.
- To backout in-flight work from an online reorganization, you must run a batch backout using a DL/I region type.
- To use a type-2 command to start an online reorganization for a HALDB partition, you must have an IMS Common Service Layer that includes the Operations Manager and the Structured Call Interface.
- HALDB Online Reorganization runs only in a local storage option-subordinate (LSO=S) environment, in which DL/I runs in a separate address space. IMS rejects attempts to initiate an online reorganization for a HALDB partition in a local storage option-yes (LSO=Y) environments.
- You cannot perform an online reorganization for a HALDB partition from an alternate IMS system in an XRF complex. However, after an XRF takeover, the new active IMS system will continue a reorganization that was active when the takeover process began.
- You cannot issue the following commands for a HALDB partition
while it is being reorganized online:
/START DATABASEorUPDATE DATABASE NAME(name) START(ACCESS)/DBRECOVERY DATABASEorUPDATE DATABASE NAME(name) STOP(ACCESS)/DBDUMP DATABASEorUPDATE DATABASE NAME(name) STOP(UPDATES)/STOP DATABASEorUPDATE DATABASE NAME(name) STOP(SCHD)
If you issue any of these commands for a HALDB partition that is actively being reorganized online, IMS displays error message DFS0488I with return code 58 and does not process the command for the named partition.
- You cannot issue the following commands for a HALDB master while
any of its partitions is being reorganized online:
/START DATABASE ACCESS UPorUPDATE DATABASE NAME(name) START(ACCESS)/DBRECOVERY DATABASEorUPDATE DATABASE NAME(name) STOP(ACCESS)/DBDUMP DATABASEorUPDATE DATABASE NAME(name) STOP(UPDATES)