SMSAUDIT function - syncsort_allocation_control_center - Latest

The SMSAUDIT utility provides the storage administrator with a means of comparing the contents of one SMS Source Control Data Set (SCDS) with a second SCDS or with the currently active SMS configuration (ACTIVE). SMSAUDIT can compare every attribute in each SMS construct to the corresponding attribute in the same construct in the second SCDS or the ACTIVE configuration, identifying instances where the two configurations differ. The comparisons can be limited to particular types of constructs (data class, storage class, and so on). Missing or changed constructs are easily identified in SMSAUDIT output. Each attribute for a construct for a CDS is displayed in a side-by-side comparison with the same attribute for the corresponding product in the second CDS.

Using SMSAUDIT, the storage administrator can ensure that the contents of an SCDS have not been changed, or if changes have occurred, that only the desired constructs and attributes have been changed.

This capability can be extremely useful in auditing, debugging, and maintaining the integrity of the SMS Control Data Sets, a vital resource in any z/OS installation.

SMSAUDIT can also take a single SCDS as input, allowing users to obtain a simple batch display of all of the attributes of a desired construct, or of the entire SCDS.

Using the SMF recording facility, this feature allows SMSAUDIT to create an "audit trail" of SMF records which can be used to provide a history of changes to a configuration, allowing administrators to determine what the most recent changes to the configuration were, and when and by whom they were made.

By default, the following types of constructs are compared:

• Base Configuration
• ACS Routine Headers
• Data Class
• Storage Class
• Management Class
• Storage Group
• Aggregate Group
• Tape Library
• Copy Pool
• Cloud
  Note: The following constructs are not currently compared, but may be included in a future release:
• Volume Definition
• Cache Structure
• Lock Structure

SMSAUDIT Output

SMSAUDIT runs as a batch job and provides two types of output:

• The SUMMARY dataset provides a summarized list of constructs (one per line) and a count of differences for each construct. Missing constructs are indicated by asterisks. The total number of constructs and differences are provided at the end of the summary.
• The SYSPRINT dataset provides a detailed display of each construct compared, with any differences between the attributes highlighted for easy identification. The total number of attribute differences are shown, along with the number of different constructs examined (for example, the number of data classes, etc.). Filters are available to limit the types of constructs compared (for example, only compare data classes, storage groups, and so on).

SMF Recording

SMSAUDIT can write an SMF record for each construct in an SCDS. This is probably most useful when running SMSAUDIT using a single SCDS to provide an SCDS history. The record consists of a standard SMF record header with the current date and time, and includes the construct name, most recent change date and time for the construct, and the userid that made the most recent change.

Running a report on the SMF records allows administrators to determine when a construct was changed and who made the change. If desired, the SCDS can then be restored from a backup and SMSAUDIT can be run to compare the restored SCDS to the current version, allowing the exact changes since the SMF record was created to be identified.