Add File to Audit Archive Tape
Add a file to the audit archive tape, which is generated by the MICS WEEKLY, or the standalone AUDIT operational job.
micsrm140
Required roles: systems programmer, security administrator, database administrator |
|---|
Follow these steps:
- Edit the FILE statement in sharedprefix.MICS.GENLIB(cccGENIN). Change the "N" in that file's audit archive position to "Y".For more information about the GENIN FILES statement, see Tailoring Archive Files.
- Submit the sharedprefix.MICS.CNTL(cccCGEN) job to regenerate the component.
- Edit prefix.MICS.PARMS(DBMODEL) for all database units in which the component is installed.On the FILE statement for the file to be added, either omit an AUDIT keyword, in which case the definition from cccGENIN is taken, or define AUDIT(YES). Audit archive is created from the DETAIL time-span. If no DETAIL time-span file cycles exist, it is created from the DAYS time-span. To create audit archive from the DAYS time-span, define AUDIT(DAYS). Define AUDIT(NO) in units where you do not want to create this file.For more information about the FILE statement in DBMODEL, see Data Retention Specifications (FILE Statement).
- Submit the prefix.MICS.CNTL(CYCLEGEN) job for all database units in which the component is installed.This job changes the component's executable code in the prefix.MICS.USER.SOURCE libraries and affects only the database units in which the component is installed.
- Edit prefix.MICS.PARMS(JCLGENU) for all database units in which the component is installed. Specify:WEEKLY AUDIT
- Submit the prefix.MICS.CNTL(JCLGENU) jobs.This generates the WEEKLY or AUDIT or both job JCL that contains DD statements for the new audit tape configuration.
- Submit prefix.MICS.CNTL(GDGSGEN) for all database units in which the component is installed.This generates audit tape file catalog indexes for the new audit file, if necessary.
For example, assume that the NPANCP file example showed the file appearing in the following archives:
WEEKLY WEEKLY MONTHLY AUDIT HISTORY HISTORY -------- -------- -------- NO YES YES
Assume that the desired configuration is:
WEEKLY WEEKLY MONTHLY AUDIT HISTORY HISTORY -------- -------- -------- YES YES YES
The initial definition of the NPANCP FILE statement in sharedprefix.MICS.GENLIB(NPAGENIN) is:
FILE NCP 00 1 Y Y Y Y N N Y Y NCP Activity File | | | no WEEKLY audit-------+ | | WEEKLY history ---------+ | MONTHLY history-----------+
Change this statement to:
FILE NCP 00 1 Y Y Y Y N Y Y Y NCP Activity File | +- WEEKLY audit produced
The number of cycles of the file that
MICS
uses as input to the weekly audit archive is fixed at ten. This means the last ten cycles of DETAIL (or DAYS if DETAIL does not typically exist) are copied to the new generation of the audit archive tape when the audit is generated in the WEEKLY or the standalone AUDIT operational job. If both DETAIL and DAYS are active, the DETAIL time-span files are used. You can specifically request audit archive from the DAYS time-span with the AUDIT(DAYS) keyword on the FILE statement in prefix.MICS.PARMS(DBMODEL).The test of what observations to put on the audit file is: any observation from a week other than the current week is copied to the audit file. Any observation that belongs to the current week is ignored, and is not copied to the audit file. If fewer than ten cycles of the file exist in the DETAIL time-span, a data loss may occur.
The intent of using ten cycles of DETAIL data is to be able to copy the entire previous week of DETAIL data to the audit file, if the WEEKLY (or AUDIT) job was run as late as WEDNESDAY of the following week. The normal WEEKLY (or AUDIT) job is run by Tuesday. Normal cycle distribution looks like:
Cycle number of associated data as of the time the WEEKLY is run on Tuesday Day of Week of -+------------------------------ Week Year | --------- -------- -+- Friday week n-2 11 Saturday 10 --+ --------+ ------------------------ | | Sunday week n-1 09 | copied | Monday | 08 | to | Tuesday | 07 | audit | considered Wednesday | 06 | | for Thursday | 05 | | audit Friday | 04 | | Saturday V 03 --+ | ------------------------ | Sunday week n 02 | Monday | 01 ------------+ Tuesday V
Data loss can occur from such conditions as:
- Fewer than nine cycles of DETAIL data are maintained
- The WEEKLY (or AUDIT) job is run as late as Thursday
- TheMICS data elementWEEK has been modified to have a value incompatible with the previous structure.
- The standalone AUDIT job is executed more than once in a given week, there is fewer than ten cycles and prefix.MICS.PARMS(EXECDEF) does not containUSERDEF AUDITCWK YES