Changing what audits are checked for compliance - assure_mimix - 10.0

Assure MIMIX Operations Guide

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Operations Guide
Copyright
2023
First publish date
1999
Last updated
2024-03-12
Published on
2024-03-12T11:06:36.794496

You can determine what audits will be included in checks for compliance with the Audits included for compliance (AUDINCMPL) policy. For each audit that you have checked for compliance, MIMIX evaluates whether the last run of the audit exceeds the days specified for the compliance warning threshold and audit action threshold policies. When an audit is approaching or is out-of-compliance, a compliance status value is reflected in the overall audit status and is included when auditing status is rolled up to other areas of a MIMIX instance.

The default behavior uses the value *BOTH, which means that both the existing configuration entries and any applicable audit options are considered when determining what audits are evaluated for compliance. This prevents the potential for compliance errors for audits that have no configured objects to audit. The File Member Record Count (#MBRRCDCNT) audit is never evaluated for compliance when the value of the FILDTA audit percent. options (FILDTAOPT policy) is 100. For a detailed description of this value and other possible values, press F1 (Help) for the Audits included for compliance (AUDINCMPL) policy in the Set MIMIX Policies (SETMMXPCY) command.

Note: This procedure changes a policy value at the installation level. The installation level value can be overridden by a data group level policy value. Therefore, if    a data group has a value other than *INST for this policy, that data group-level value remains in effect regardless of the instance-level value.
  1. From the command line type SETMMXPCY and press F4 (Prompt).

  2. Verify that the value specified for Data group definition is *INST.

  3. Press Enter to see all the policies and their current values.

  4. For Audits included for compliance (AUDINCMPL), either specify a value (*BOTH, *ALL, *AUDOPT, or *CONFIG) or use the “+ for more” fields as needed to specify one or more audit names.

  5. To accept the changes, press Enter.