Restrictions: Cases where DMB verification is not done

DMB verification is not done for IMS™ batch programs, IMS utility programs, or IMS Tools programs when these jobs are run with DBRC inactive (DBRC=N). Also, even when DBRC is active (DBRC=Y), DMB verification is not done when certain tools are used or under certain conditions.

  • Even when DBRC is active, DMB verification is not done for the following utility jobs:
    IMS standard utilities
    • Database Prefix Resolution utility (DFSURG0)
    • MSDB to DEDB Conversion utility (DBFUCDB0)
    • Database Prereorganization utility (DFSURPR0) (for non-HALDBs)
    • Database Change Accumulation utility (DFSUCUM0)
    • Batch Backout utility (DFSDB000)
    • HISAM Reorganization Unload utility (DFSURUL0)
    • DEDB Initialization utility (DFSUMIN0)
    • Database Image Copy utility (DFSUDMP0) (for HALDBs)
    • Database Image Copy2 utility (DFSUDMP0) (for HALDBs)
    IMS Tools products
    • IMS High Performance Prefix Resolution
    • IMS High Performance Pointer Checker (for HALDBs)
    • IMS Fast Path Advanced Tool and IMS Fast Path Basic Tools of IMS Fast Path Solution Pack
  • To activate DMB verification in IMS Index Builder jobs, APAR PM53350 must be applied to IMS Index Builder, and IMS Index Builder JCL must specify DBAUTH YES (default). Otherwise, DMB verification is not done.
  • DMB verification cannot be used in IMS Fast Path Advanced Tool and IMS Fast Path Basic Tools jobs of IMS Fast Path Solution Pack.
    • DMB verification is supported in IMS Fast Path Online Tools jobs.
    • Integrity Checker can update RDEs and record time stamps when it is called in IMS Fast Path Advanced Tool jobs.
  • When a database authorization request is made by the DBRC application programming interface (API), Integrity Checker does not verify the DMB.
  • In an XRF environment, the alternate subsystem inherits databases and their authorization from the active subsystem during takeover. Integrity Checker does not verify the DMBs in the alternate subsystem (that is, the new active subsystem) until the databases are stopped by the /STOP or the /DBR command, and then restarted by the /START command.
  • In Fast Database Recovery (FDBR) regions, FDBR does not require authorization for any databases to be recovered. Consequently, Integrity Checker does not verify the DMBs in FDBR regions.
Parent topic: Preventing database corruption with Integrity Checker