The process of auditing consists of a compare phase and a recovery phase.
In the compare phase of an audit, the identified audit rule initiates a specific compare command against the data group. The Audit runs policy determines if an audit is allowed to run. The Auditing Options policies, available for a subset of audits, determine how aggressively an audit checks your environment during its compare phase. If a shipped audit rule provides more than one audit option, each option provides increasingly more checking capability.
If there are detected differences when the compare phase completes, the audit enters its recovery phase to start automatic recovery actions as needed. Recovery actions for audits that compare attributes (#DLOATR, #FILATR, #FILATRMBR, #IFSATR, and #OBJATR audits) are submitted to the MIMIX Replication Manager (MXREPMGR) for processing, where multiple recovery actions for an audit run in parallel. The difference indicator value is *RCYSBM. The audit does not wait for the recoveries to complete before the audit completes and considers the submitted recoveries as successes towards the overall audit results status.
If the submitted recovery action fails or the object cannot be recovered, the object is identified on the appropriate display (Work with DG File Entries, Work with DG Activity Entries, Work with DG IFS Trk. Entries, or Work with DG Obj. Trk. Entries). From any of these interfaces, you can take manual recovery actions to synchronize the object the same as if its error had been originally detected by replication processes.
For the few remaining types of audit recoveries performed by the audit and not handled by MXREPMGR, MIMIX is shipped with defaults that enable audits to enter the recovery phase automatically when needed. The recovery phase can be optionally disabled in the Automatic audit recovery policy. The duration of an audit's recovery phase is the amount of time needed to submit and perform recoveries. During the recovery phase, MIMIX attempts to correct the differences and sends reports to the user interface. Only those recoveries that are still active or are in process of ending are displayed in the interface. If the recovery job fails to correct the problem, MIMIX removes the recovery and sends an error notification to the user interface.
If the data group is inactive or exceeds its database apply threshold when the audit runs and the value of the Action for running audits policy (RUNAUDIT) in effect is Compare Recover (*CMPRPR), any recovery actions for differences detected by the audit are queued for the replication manager and will be processed after the data group starts or the backlog that exceeded the threshold is resolved. If the Automatic audit recovery policy (AUDRCY) is disabled, any objects with differences are reported as failed recoveries on the appropriate interfaces.