There may be scenarios when you need to disable auditing completely for either an installation or a specific data group. Auditing may not be desirable on a test data group or during system or network maintenance.
The Audit runs policy can be used to disable all auditing, including manually invoked audits.The Audit runs policy can be set for an installation or for specific data groups. Note that an explicitly set value for a data group will override the installation value and may still allow an audit to run.
You can also prevent audits from being submitted automatically for a data group while still allowing them to be invoked manually. Automatic submission of all-objects audits, prioritized audits, or both, can be prevented by changing the state specified in the audit’s schedule. For more information, see Disabling or enabling automatically submitted audits.
In addition to auditing, automatic recovery during replication may need to be prevented from running due to issues with applications or MIMIX features, For more information, see When to disable automatic recovery for replication and auditing.
The override audit policies (OVRAUDPCY) parameter on the Run Rule (RUNRULE) command specifies whether a run of the specified audits will override the auditing policies specified in Audit runs (AUDRUN) and Audit options (FILDTAOPT, IFSAUDOPT, and DLOAUDOPT). Option 39 on the Work with Audits display provides the same functionality.