You can control the severity associated with the audit status values *NOTRUN and *IGNOBJ. The severity determines whether these status values are considered errors, warnings, or informational when auditing status is rolled up to other status values within a MIMIX™ Software instance. The severity associated with *NOTRUN and *IGNOBJ statuses affects the order in which audits are listed on the Work with Audits display (WRKAUD command) and in the Audits portlet in the Assure Unified Interface, and the icon associated with these statuses in the Audits portlet.
All audit statuses have an associated severity. Only the severity associated with these statuses can be changed with the Audit severity (AUDSEV) policy:
-
*NOTRUN - indicates that an audit was submitted but did not run due to the status of replication processes or policy settings.
-
*IGNOBJ - indicates than an audit could not check some objects, typically due to replication activity, locks, or authorizations. All other objects checked were considered equal or had detected differences that were automatically recovered.
The policy setting for the severity of the *IGNOBJ status also affects whether any ignored objects are counted as differences. The policy’s effect on how ignored objects are counted occurs regardless of whether the audit status is *IGNOBJ or a more severe audit status.
-
From the command line type SETMMXPCY and press F4 (Prompt).
-
Verify that the value specified for Data group definition is *INST.
-
Press Enter to see all the policies and their current values.
-
For Audit severity, do the following, as needed:
-
At the Not run audit status prompt, specify the severity value (*ERROR, *WARNING, or *INFO) to associate with the audit status *NOTRUN.
-
At the Ignored objects audit status prompt, specify the severity value (*WARNING or *INFO) to associate with the audit status *IGNOBJ.
-
-
To accept the changes, press Enter.