4. Operation › 4.1 Overview

4.1 Overview

To help you operate CA MICS, this overview describes the
significance of operational procedures (why things must be
done).  You should read this entire section before proceeding
to Operational Guidelines, Reference, or Administration.

A CA MICS complex is one installed copy of CA MICS.  It
consists of the following:

  o One or more CA MICS unit databases

  o sharedprefix and prefix libraries - programs, JCL,
    CLISTs, parameter definitions, and documentation

  o Application Databases - SAS data files not subject to
    time sequence data, summarization, or aging rules.  The
    TABLES data area (or file) is one example.  The Change
    Tracking File provided in the Batch and Operations
    Analyzer's Operations Information Area is stored in the
    TABLES area.

The CA MICS Database is updated periodically (daily, weekly,
monthly, and yearly).  The update processes must be closely
monitored to ensure that they run serially:  each update must
complete successfully before the next update is started.

The following topics explain this requirement and describe
facilities to ensure that sequential updates take place:

   1 - CA MICS Database Organization
   2 - Operational Processes, Jobs, and Steps
   3 - Processing Schedule
   4 - Restart Facility
   5 - Select and Force Facilities
   6 - Checkpoint File
   7 - Database Update Audit Trail
   8 - Operational Status and Tracking Facility
   9 - Administrative Activities