Don’t understand how RC error was triggered by update if not running a BA24, but a DDUPDATE to perform the following, while the database was still open to the MUF:
-UPD AREA,area_name(PROD)
1000 ALTER
1500 BLOCK-SIZE,04096
1500 DYNAMIC-EXTEND,C
1500 DYN-EXT-TRACKS,00100
-END
+UPD DATABASE,database_name(PROD,PRIV)
1000 ENABLE
+END
/*
The plan was to BACKUP the area, INIT it to the new block size blksize and LOAD it from the BACKUP.
This problem occurs when the MUF is started with the AREA_BLOCK_SIZE_ALTER YES option. This option is used to allow a DDUPDATE to alter the block size of a DB Area via the Block Size Alter (24x7) utility, which requires a PREINIT of the Area or other prerequisites before invoking BA24 via DDUPDATE.
Check the MUF log after the failed DDUPDATE to see more elaborate details on the failure. For example (for DBID:493 and Area:A01), when starting the MUF with the mentioned option without performing an INIT or PREINIT of the IXX and the Area, the following messages were generated:
MUFNAME:DB02832I - ONLINE_BA24_MOVE 493 A01 STATUS PREPARING TO START
MUFNAME:DB01401E - MVS DYNAMIC ALLOCATION ERROR, DDNAME=IXX493 , R15=4, ERROR=1708, INFO=0002
MUFNAME:DB01417E - DYNALLOC ERROR, IXX493 DCMQA.QAMUFT.IXX493
MUFNAME:DB00501E - OPEN ERROR - RETURN CODE 74 (081) CXX=QAMUFT (IXX00493) ***MOVDS JOB58710
MUFNAME:DB02405I - PXX START ***MOVDS 0 PATCH ONLBA-493-A01 D-2 CONSOLE BLK.SIZE
MUFNAME:DB02406I - PXX END - PATCH COM 5A34
MUFNAME:DB02817E - ONLINE_AREA_MOVE 493 A01 ERROR OPEN FROM 74(81)
MUFNAME:DB00113I - BACKOUT JOB-DDUPD NUMBER-96075 RC= Y TSN-00009475
MUFNAME:DB00151I - ENDED DDUPD 96075 JOB26346-1 RQ-928 IO-51 E-M:S-0:1 R-M:S-0:0.01 DS
Then, after recycling the MUF without the AREA_BLOCK_SIZE_ALTER YES startup option, the DDUPDATE worked successfully.
With this in mind, please refer to BA24_DISPOSITION_NEW (Block Size Alter 24x7) section from Datacom Core15.1, which shows the following alternative and preferred way to perform the Block Alter (24x7):
Due to the introduction of the console command ONLINE_BA24_MOVE, this start-up option is no longer recommended. The best practice is to use the ONLINE_BA24_MOVE command. Before you use ONLINE_BA24_MOVE, remove or comment out AREA_BLOCK_SIZE_ALTER YES and BA24_DISPOSITION_NEW YES and then recycle the MUF.