4. Operation › 4.2 Operational Guidelines › 4.2.3 Monitoring CA MICS Operations

4.2.3 Monitoring CA MICS Operations

CA MICS is a production information system.  You should
monitor daily operations to ensure that the CA MICS Database
is updated correctly and on time.

Use Operational Status and Tracking to monitor daily CA MICS
operations.  The primary Operational Status and Tracking
display lists the current status for each unit database.
Overdue processing and database update failures are noted.

  o The STATUS command provides additional details relating
    to unit database status and error conditions.

  o The HISTORY command displays the Database update audit
    trail (ADMIHL file).

  o The JOBLOG command displays a processing audit log.

  o You can override the default Overdue time-of-day (8:00
    a.m.) for each CA MICS unit database on the Operational
    Status and Tracking display by scrolling RIGHT MAX and
    changing the 8 a.m.  default deadline.

Review printed outputs from production CA MICS processing.
Printed outputs include JCL logs, MICSLOG, and SAS log.

  o The Run Status Report describes the result of current
    processing.  This information is also available with the
    Operational Status and Tracking STATUS command.
  o The MICSLOG reports the status of each production job
    step.  Database update steps report the number of input
    records processed and log the records deleted due to
    date-range, record length, and other validation tests.
    This information is also available with the Operational
    Status and Tracking HISTORY command.

    - Verify that the number of input records processed is
      reasonable for your normal processing.  For example, a
      low value may indicate missing input data, while a high
      value might indicate duplicate input or new workloads.

    - Investigate the cause for deleted (or dropped) input
      records.  For example, records deleted due to
      checkpoint date may indicate reprocessing of old input
      (duplicate) data.

Retain printed outputs from production CA MICS processing.
As a guideline, consider keeping printed outputs until the
corresponding input data or weekly/monthly/yearly cycle ages
off of the Database.