Using the enhanced audit command to audit DFSMShsm control information

Table 1 lists the AUDIT commands audit and report errors within DFSMShsm controls and where to find more information.

Table 1. AUDIT Commands that Audit and Report Errors
If the command you are interested in is. . .	Then see. . .
AUDIT ABARSCONTROLS (agname)	Using the AUDIT ABARSCONTROLS command
AUDIT COMMONQUEUE	Using the AUDIT COMMONQUEUE command
AUDIT COPYPOOLCONTROLS	Using the AUDIT COPYPOOLCONTROLS command
AUDIT DATASETCONTROLS (BACKUP)	Using the AUDIT DATASETCONTROLS (BACKUP) command
AUDIT DATASETCONTROLS (MIGRATION)	Using the AUDIT DATASETCONTROLS (MIGRATION) command
AUDIT DIRECTORYCONTROLS VOLUMES	Using the AUDIT DIRECTORYCONTROLS command
AUDIT MEDIACONTROLS (SDSP) VOLUMES	Using the AUDIT MEDIACONTROLS (SDSP) VOLUMES command
AUDIT MEDIACONTROLS (VOLUMES)	Using the AUDIT MEDIACONTROLS VOLUMES command
AUDIT VOLUMECONTROLS (BACKUP)	Using the AUDIT VOLUMECONTROLS (BACKUP) command
AUDIT VOLUMECONTROLS (MIGRATION)	Using the AUDIT VOLUMECONTROLS (MIGRATION) command
AUDIT VOLUMECONTROLS (RECOVERABLE)	Using the AUDIT VOLUMECONTROLS (RECOVERABLE) command

When the FIX parameter is specified, AUDIT often completes repairs. There may be times, however, when you want to audit without fixing errors. During an audit, the AUDIT function serializes control records, which allows it to compare several sources of information. While the control records are serialized, they are static and the comparisons are valid. Once the audit has completed, the system returns to its normal dynamic mode, and these comparisons may no longer be valid.

Your decision concerning the use of the FIX parameter to repair errors depends mostly upon two factors:

First, how busy is DFSMShsm? The higher the activity, the faster your audit report becomes obsolete.
Second, what is the scope of your audit? If you just want to check the status of one DASD volume, then running AUDIT without the FIX parameter will be helpful. If you audit many controls, your report becomes obsolete quickly.

When auditing a common queue, FIX does not create the same concerns as when auditing other controls. In general, FIX should always be specified when auditing a common queue.

When using the AUDIT functions listed in topic One, you receive important information in the report header and the report body:

The header of your audit report confirms the performed audit and shows the time, the date, and the system identification. The second line of the report header reflects the AUDIT command and parameters that you have entered.
The body of your audit report normally consists of two lines printed for each detected error. The first line gives you the error code and a brief description of the error. The lines immediately following the error code list the appropriate repair commands whenever the AUDIT function is able to identify them.

AUDIT COMMONQUEUE does not generate a report. The only output of AUDIT COMMONQUEUE is message ARC1544I.

During an audit, AUDIT executes the following sequence:

DETECTION: AUDIT checks for inconsistent sources of information that might prevent DFSMShsm from retrieving a data set (or group of data sets), or accessing a DFSMShsm-owned volume.
DIAGNOSIS: AUDIT attempts to refer to one or more additional sources of information (a reality outside of the conflicting sources), when it detects an inconsistency. In many instances, AUDIT is able to list either a repair action (FIX) or a recommendation for further diagnosis of the detected error.
FIX: AUDIT initiates repair action, when you specify the FIX parameter and when AUDIT determines the appropriate FIX.

You can determine whether repair action has been initiated by examining two items on the audit report. When FIX is specified for a common queue, all detected errors will be fixed. No specific information is given concerning each error.

Was the FIX parameter specified?
Did AUDIT list the appropriate repair action?