4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.19 AUDIT Operational Job

4.3.3.2.19 AUDIT Operational Job

The AUDIT job applies only where you have activated
stand-alone Archive Audit tape processing by specifying

     ARCHIVE AUDIT YES JOB

in prefix.MICS.PARMS(JCLDEF).
The AUDIT job performs the Archive Audit tape processing.
This processing alternatively occurs within the WEEKLY job's
WEEK300 step.

Archive audit data is created as a new entry in the audit
generation data group.  The audit data is generated for files
that contain job, program, command, or application unit
execution-related data by copying data from the last ten
DAILY or DETAIL timespan cycles maintained online for the
applicable files.  If the file is active in the DETAIL
timespan, DETAIL is used.  If the file is NOT active in the
DETAIL timespan, then DAYS is used.
The files included in archive audit processing are specified
in prefix.MICS.PARMS(DBMODEL) and sharedprefix.MICS.GENLIB
member cccGENIN, where ccc is the three-character component
identifier.  Archive audit tape retention (number of
generations) is specified in prefix.MICS.PARMS(JCLDEF).  See
the CA MICS Structure and Content Guide for more information
on the Archive Database.
The AUDIT job may be scheduled automatically, or you may need
to schedule the job using your installation's production
batch job scheduling facilities.

o  If you specified

        ARCHIVE AUDIT YES JOB

   in prefix.MICS.CNTL(JCLDEF), then Archive Audit processing
   is performed in the stand-alone AUDIT job.

   -  If you specified the AUTOSUBMIT parameter on the
      ARCHIVE statement, then the WEEKLY job WEEK300 step
      automatically submits the AUDIT job through the OS/390
      internal reader.

   -  If you specified NOAUTOSUBMIT (or took the default)
      then you must schedule the AUDIT job externally, either
      manually or through your installation's production
      batch job scheduling facilities.

   NOTE:  The AUDIT job must complete before the next
          scheduled DAILY job will be allowed to execute.
o  If you specified

        ARCHIVE AUDIT YES

   in prefix.MICS.CNTL(JCLDEF), without the JOB parameter
   (i.e., you took the default or specified STEP), then
   Archive Audit processing is performed in the WEEK300 step
   of the WEEKLY job.  In this situation, you will NOT
   execute the AUDIT job.
You will normally execute the AUDIT job once each week, after
the WEEKLY job completes successfully.  However, you can
choose to run the AUDIT job more often.  Each time AUDIT
executes, it will create a new audit tape cycle from the
contents of the last 10 online cycles of the database files
for which audit is enabled.

o  Note, by default, audit archive processing drops data from
   the current week in order to reduce processing time and
   conserve CA MICS tape data base space.  Thus, even though
   10 cycles of data are input, depending upon when audit
   archive processing is performed, the full 10 online cycles
   my not be included in the current audit archive tape
   cycle.
o  You may find that you can reduce the number of cycles
   retained online by executing the AUDIT job more frequently
   (e.g., 4 times per week) and then referring to the audit
   tapes when detail data analysis is required.

   Note: If you choose to take advantage of this technique,
   and execute the AUDIT job more often than once each week,
   then the following must be added to
   prefix.MICS.PARMS(EXECDEF)

    USERDEF AUDITCWK YES
   This parameter overrides the default audit archive
   processing so that data for the current week is retained
   and copied to the new audit archive tape cycle.

   Concurrently, don't forget to increase the number of
   cycles of the archive audit tapes you retain (see the GDG=
   subparameter of the AUDITPARM statement in
   prefix.MICS.CNTL(JCLDEF).