Previous Topic: DBUTLTY INIT EnhancementsNext Topic: DBUTLTY External Security


DBUTLTY OLREORG Options to Allow Use of Empty Blocks

The CA Datacom DBUTLTY function OLREORG has been enhanced to allow the use of empty blocks in a reorganization when the amount of free space is limited in used data blocks. Support for the new OLREORG empty block includes the following categories:

Keeping Track of Empty Blocks

CA Datacom/DB keeps track of the available space of a data area using a special key ID in each DBID index. In Version 12.0, data space options 1, basic space reclamation, and 2, wraparound mode, did not keep track of which blocks were logically empty, that is, blocks that were used in the past but currently have all their rows deleted.

To enhance the efficiency of OLREORG, the following space options were added that keep track of empty blocks:

Support for these Space Management Options were added to the Datadictionary 3002 Area transaction.

Support was also added to the DBUTLTY CXXMAINT ALTER DSOP function, but we recommend that you change your space option in CA Datacom Datadictionary.

Changing the space option does not affect the loaded status of the data area and is effective immediately following its change in the CXX. Because the empty block index was not maintained in the past for basic and wraparound modes, we recommend that, when changing to a DSOP 4 or 5, you run a RETIX KEYNAME=*DATA to rebuild the space index, including the new empty block component of the space index.

Note: You are not required to run this RETIX.

External Limits

If there are no more blocks in the empty block index, OLREORG uses the next available overflow (NAO) block. OLREORG never causes a dynamic extend.