Reload DBRC considerations
When DBRC is active during execution of the reload function and the output area is registered with DBRC,
Fast Path Reorg/EP
verifies from DBRC that each output area is marked Recovery Needed. These conditions are shown in the following table. The reload function obtains exclusive access (EX) from DBRC for each output data set. No DBRC authorization is performed on the input data sets.
Command | Authorization | Recovery Needed flag |
|---|---|---|
RELOAD (area data set input) | Not applicable | Not applicable |
RELOAD (outputs) | Exclusive access (EX) | ON |
If your areas do not reflect the appropriate Recovery Needed condition, their status must be changed before execution of the reload function. To set the Recovery Needed flag ON, execute the DBRC utility by using the command shown in the following figure.
Multiple area data sets (MADS) are not supported. The reload function reloads only the first area data set that is registered in the ADS list (in collating sequence by ddname). All other area data sets are marked unavailable. When reload processing has completed, use the IBM Online MADS Create utility to resynchronize the other (unavailable) area data sets.
When reload processing is completed, the reload function resets the Recovery Needed flag and notifies DBRC that an image copy is required for each area by setting the Image Copy Needed flag. You can use the IC subcommand to request that an image copy be created for each area during reload processing. DBRC is informed (NOTIFY.IC) when this image copy is created successfully, which resets the Image Copy Needed flag.
If you do not take an image copy during the reload process, an informational message is issued for each output area to indicate that an image copy should be taken before each area can be updated online.
Related topic