4. Operation › 4.3 Operations Reference › 4.3.5 Database Update Audit Trail (ADMIHL)

4.3.5 Database Update Audit Trail (ADMIHL)

The Input History Log (IHL) file contains data identifying
the raw data that has been input for CA MICS Database
updating over the last n days, where n was defined using the
INPUTLOGLIMIT keyword in prefix.MICS.PARMS(EXECDEF).  The
data is keyed by system identifier (SYSID), product, and
update cycle.

The file is maintained in the DAYS timespan and is referenced
by the label ADMIHL01.  It is only maintained for one cycle,
so it is always referenced as &pADMD..ADMIHL01 where p is the
unit Database ID.  For more information about the file, refer
to the CA MICS Database Structure and Content Guide, section
2.2.

You can browse the Input History Log via the online
Operational Status and Tracking facility (HISTORY command) or
by using distributed MICF inquiries (e.g., BASLA1, CA MICS
Daily Processing Summary).

The following diagram illustrates how the Input History Log
File is updated.  Each DAILY job step adds information to the
IHL file for the CA MICS product or field developed
application being processed.

+-----------------------------------------------------------+
|                                                           |
|  CA MICS Daily Job Stream                                 |
|                                                           |
|  +---------------------------+                            |
|  |                           |                            |
|  |   Step DAYSMF in DAILY    |   +---------+              |
|  |  +---------------------+  |   |SYSID/   |              |
|  |  | Write SYSID/        |----->|Product  |              |
|  |  | product checkpoint  |  |   |Data     |              |
|  |  | to a temporary file |  |   +---------+              |
|  |  +---------------------+  |  /                         |
|  |                           | /                          |
|  |   Update Steps in Daily   |/ Input History Log         |
|  |  +---------------------+  /   +---------+              |
|  |  | Update Input History| /|   |SYSID/   |              |
|  |  | Log with today's    |----->|Product  |              |
|  |  | update status.      |  |   |Data     |              |
|  |  +---------------------+  |   +---------+              |
|  +---------------------------+                            |
+-----------------------------------------------------------+

When incremental update is active, audit trail information is
collected by each INCRccc job execution and maintained in the
product's incremental update DAYS level database (IUDAYS).

At the end of the day, the product's DAILY job step (DAYnnn)
"rolls-up" the incremental update audit trail information,
including audit trail data from the DAYnnn step itself to the
unit database ADMIHL01 file.

Note:  Audit trail information for incremental update
       (INCRccc job) executions is NOT reflected in the
       ADMIHL file UNTIL the associated DAILY job (DAYnnn)
       step completes.