1. Database Structure › 1.2 Database Structure and Organization › 1.2.2 Archive Data Structure › 1.2.2.1 Archive Audit Data

1.2.2.1 Archive Audit Data

The Archive Audit Data is comprised of a number of weekly
tapes, each containing the detail audit data for the jobs,
programs, commands, etc., that were executed for the week.
The files CA MICS delivers with Archive Audit enabled are
those with user identifiers, typically those on which
installation accounting is based.

The accessing of a SAS file on tape is handled no
differently than one on a disk, except for the JCL.  The DD
statement in the JCL simply points to the archive data set
name, which has been cataloged as a tape data set.  The
processing restriction is that the user may only access one
file at a time on the tape data set.

The archive audit data set is created at the end of each week
as a standard part of the weekly database update processing
(reference the Operation chapter of the Planning,
Installation, Operation and Maintenance Guide).  A generation
data group is used as the means to control the retention of
these data sets.  The data set name for the audit data is

     'tapeprefix.MICS.AUDIT.filename'

suffixed by the necessary generation data group
identification numbers.  Figure 1-10 illustrates the data set
names as they would be referenced according to their position
in the eneration data group entries.

+-------------------------------+---------------------------+
| Generation Data Set Name      | Audit Data Period         |
+-------------------------------+---------------------------+
|   MICS.AUDIT.xxxxxx(0)        | Last week's audit data    |
|   MICS.AUDIT.xxxxxx(-1)       | Audit data:  2 weeks ago  |
|   MICS.AUDIT.xxxxxx(-2)       | Audit data:  3 weeks ago  |
|                               |                           |
|   MICS.AUDIT.xxxxxx(-51)      | Audit data:  52 weeks ago |
|   MICS.AUDIT.xxxxxx(-52)      | Audit data:  53 weeks ago |
|                               |                           |
|  where xxxxxx identifies the  |                           |
|               specific File.  |                           |
+-------------------------------+---------------------------+

Figure 1-10. Archive Data Set Generation Data Groups

NOTE:  Before using Archive Audit, you should normally have
       at least seven cycles of DETAIL data available.

       Some installations may choose to create archive audit
       tapes more frequently than weekly (e.g., a site might
       run the stand-alone AUDIT job three times each week)
       and thereby will need to retain less cycles of DETAIL
       data in the online database.  See the Planning,
       Installation, Maintenance, and Operation Guide for
       more information on archive audit scheduling, the
       WEEKLY operational job, and the stand-alone AUDIT
       operational job.