Previous Topic: 2. System Overview

Next Topic: 2.2 CA MICS Naming Conventions

2.1 Installed CA MICS System


In the simplest sense, CA MICS provides a single, common
analytical process to analyze many unlike measurement
sources.  It enables you to systematically track and report
z/OS SCP, hardware, TSO, batch, and many other activities
within time-synchronized intervals.  Its database structure,
which is described below, enables CA MICS to contribute to
enterprise systems management.
Database Structure

The highest logical unit in CA MICS is a database complex.
This is a complete and independent CA MICS system. It
consists of shared complex libraries and one or more database
units.  Each database unit consists of database unit
libraries and data files.

Many organizations have a single database complex
containing at least one production database unit and one
test unit.  Organizations that run CA MICS at multiple sites
typically have a database complex at each site.  Figure 2-1
depicts a database complex with three database units.

+-----------------------------------------------------------+ |                                                           | |                      +-------------+                      | |                      |  CA MICS    |                      | |                      |  Shared     |                      | |                      |  Complex    |                      | |                      |  Libraries  |                      | |                      +-------------+                      | |                             |                             | |                             |                             | |         +-------------------+-----------------+           | |         |                   |                 |           | |  +-------------+     +-------------+   +-------------+    | |  |  Primary    |     |    Unit     |   |    Test     |    | |  |  Database   |     |  Database   |   |  Database   |    | |  +-------------+     +-------------+   +-------------+    | |         |                   |                 |           | |  +-------------+     +-------------+   +-------------+    | |  |    Unit     |     |    Unit     |   |    Unit     |    | |  |  Database   |     |  Database   |   |  Database   |    | |  |  Libraries  |     |  Libraries  |   |  Libraries  |    | |  +-------------+     +-------------+   +-------------+    | |                                                           | +-----------------------------------------------------------+

 Figure 2-1.  Sample CA MICS Database Complex
Database Complex

The CA MICS system is installed as a group of one or more
database units which share some libraries and data areas.
The entire structure of data and code libraries is called a
database complex.

The shared libraries contain programs, JCL, macros, parameter
definitions, and documentation.  The shared data areas
include TABLES (used mostly by CA MICS Accounting and
Chargeback), MCOLIB (a system control area), CAPACITY, etc.
They contain SAS data files which apply to the entire complex
and not just a particular database.
Database Unit(s)

In addition to the shared libraries, a database complex
consists of database units.  Each database unit contains
data files and libraries of code, JCL, and parameters needed
to define, update, and access these data files.

Database units may be one of four types:  primary, unit,
test, or special.  Each type of unit is treated differently
by the JCLGEN process and by CA MICS Accounting and
Chargeback.  The purpose of each is described below.

 Primary - Every database complex contains only one primary
           database unit.  The distinguishing feature of a
           primary database unit is that its backup process
           backs up the MCOLIB, SCREENS, TABLES, ISPTLIB,
           etc., data sets that exist at the complex level.

 Unit -    A normal production database is called a unit
           database.  Every unit database contains CA MICS
           Platform (BAS) plus one or more other products.
           Any combination of products is allowed, with the
           exception that CA MICS Accounting and Chargeback,
           if installed, must accompany at least one product
           that supports accounting.

 Test -    A test database unit is used for developing user
           components and testing user modifications to the
           CA MICS system. It is also used when installing
           maintenance and new versions of the system.  Test
           database units differ from unit databases in
           that they are treated specially by CA MICS
           Accounting and Chargeback and the CA MICS JCL
           generation process.  Jobs run on a test unit use
           special test libraries that are concatenated ahead
           of the standard libraries.

 Special - Special databases are temporarily added to the
           CA MICS complex to perform special studies
           involving data not available in the production
           databases.  A special unit can also be used for
           certain configuration planning and testing
           functions (through modifications to parameter
           library modifications).
More Information

For more information about the data sets that comprise a CA
MICS system, see the section 4.3 in the PIOM.