Use this command to ensure that the database is returned to a synchronized state after it is reloaded by issuing the DSMSERV LOADDB command. A message at the end of the output from the DSMSERV LOADDB command indicates whether this command is required. Issue this command before starting the server, and do not restart the server until the command has completed processing.
Issue this command only if one of the following conditions is true:
Note: | If the recovery log mode was set to roll-forward before the server was halted, set the recovery log mode to normal before issuing the DSMSERV AUDITDB utility. This action will avoid running out of log space during DSMSERV AUDITDB processing. |
No other server activity is allowed during DSMSERV AUDITDB processing.
Note: | If STANDARD policy objects are deleted before TSM reinstallation, you will receive a message during the audit processing indicating that an instance count does not agree with actual data. If you delete the STANDARD policy objects, they are restored during reinstallation. The command does not delete the objects. Instead, it synchronizes the instance count to include the restored objects. |
Syntax
.-FIX--=--No------. >>-DSMSERV AUDITDB----+-----------------+-----------------------> '-FIX--=--+-No--+-' '-Yes-' .-Detail--=--No------. >-----+--------------------+---+---------------------+--------->< '-Detail--=--+-No--+-' '-FILE--=--file_name--' '-Yes-'
Parameters
If the audit finds inconsistencies, re-issue the command specifying FIX=YES before making the server available for production work. Because AUDITDB must be run with FIX=YES to recover the database, the recommended usage in a recovery situation is FIX=YES the first time.
Examples
Task
Audit the TSM database for inconsistencies, but do not fix inconsistencies if they exist.