When attempting to enable Dynamic Extend for a Datacom Table or Index via a DDUPDATE job, the Multi-User Facility (MUF) JES log may display messages that are not expected for a simple attribute update. These messages include:
DB02832I - ONLINE_BA24_MOVE [dbid] [area] STATUS PREPARING TO STARTDB02831E - ONLINE_BA24_MOVE [dbid] [area] ERROR NO PREINITDB00113I - BACKOUT JOB-[jobname] NUMBER-[number] RC= Y TSN-[tsn]Users may be concerned that these messages indicate a failure in setting up Dynamic Extend or a conflict with the Data Dictionary updates.
These messages occur because the MUF is configured with the legacy startup option AREA_BLOCK_SIZE_ALTER YES.
This option triggers the Block Size Alter (24x7) utility logic whenever an area update is submitted through DDUPDATE. Even if the user is only updating the DYNAMIC-EXTEND or DYN-EXT-TRACKS attributes, the MUF attempts to prepare for a block size alteration process. If the environment is not specifically staged for that utility (e.g., missing pre-initialization), it results in the DB02831E error and a subsequent backout of the utility task, though the DDUPDATE itself may still complete.
These messages are not relevant to the successful configuration of Dynamic Extend and indicate unnecessary processing within the MUF. To prevent these messages and streamline area updates, follow these steps:
AREA_BLOCK_SIZE_ALTER YESBA24_DISPOSITION_NEW YES (if present)Note: These options are no longer the recommended method for altering block sizes and should be removed to avoid interference with standard administrative tasks. Please see this note in the documentation for more details.