• IMS V8 Database Recovery Control Enhancements include:
• Automatic Recon Loss Notification adds support to automatically propagate a Recovery Control Data Set (RECON) reconfiguration to other DBRC instances. When an error on a RECON data set results in a RECON reconfiguration on one IMS subsystem, other DBRC instances using the same RECONs are notified. The result is that all IMS subsystems automatically deallocate the failed RECON data set so that the user can quickly recover from the loss.
• Eliminate abends - When authorizing databases or recording Extended Error Queue Elements (EEQEs), DBRC would no longer ABEND and be less likely to cause IMS to ABEND due to RECON record size problems. DBRC also would no longer abend when attempting to deallocate a database that is recorded in RECON as "already deallocated".
• RECON Command Authorization support allows users to control RECON access/update via DBRC batch commands as well as the High Availability Large Database (HALDB) Partition Definition Utility. User exit implementation allows user flexibility to customize security criteria and maintain an audit trail. This helps customers protect the integrity of database data by allowing finer control over the data one can access.
• 16M RECON Record Size helps users avoid problems caused by RECON records (such as the PRILOG record which identifies the primary log for an active system) exceeding the VSAM RECORDSIZE maximum. This eliminates planned and unplanned outages that are due to RECON record size. DBRC implements its own RECON record spanning.
• Prilog Compression has been enhanced to reduce its overhead, improving performance. Since DBRC now supports RECON records of unlimited size, compression is attempted whenever an Online Log Data Set (OLDS) is archived.

---