|
|
|
The CA MICS system is installed at a site as a group of one
or more databases which share some libraries and data areas.
The entire structure of data and code libraries is called a
database complex. A sample database complex is shown in
Figure 1-1.
+-------------------------+
| Database Complex |
+-------------------------+
| |
| Shared System Libraries |
| |
| Shared Data Areas |
| |
+------------+------------+
|
|
+--------------------+------------------+
| | |
| | |
+------+----------+ +------+-------+ +-------+------+
| | | | | |
|Primary Database | |Unit Database | |Test Database |
| | | | | |
+-----------------+ +--------------+ +--------------+
Figure 1-1. Database Complex Overview
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.
In the example above, the database complex consists of
three databases (also called database units or unit
databases). Each database contains data files and libraries
of code, JCL, and parameters needed to define, update, and
access these data files.
The different types of databases and their uses follow.
Unit - This is a normal production database.
Primary - Every database complex contains a primary
database. It is a database unit which is used to
store some JCL which is kept at the database unit
level, but which need not be stored in every
database unit.
Test - A test database is used for developing user
components and testing user modifications to the
CA MICS system. It is a normal database unit, but
is treated specially by CA MICS Accounting and
Chargeback and by the CA MICS JCL generation
process.
Special - Special databases are added temporarily to the
CA MICS complex to perform special studies.
The data structure of every database is the same,
regardless of the type. The remainder of this section and
the sections that follow describe the structure of a single
database.
The data maintained in each database is organized and
separated according to the data's update and retrieval
requirements. Economical and usable database update and
retrieval facilities are realized through a five-way grouping
of the data. These groups are termed timespans.
The timespans provide for unique retention, sequencing,
organization, and summarization of the data. The timespans
are DETAIL, DAYS, WEEKS, MONTHS, and YEARS. The data is
further structured within a timespan.
The detail structure of the database is fully described
in this chapter.
The raw measurement data that is read in to update the
database is formatted and stored in the DETAIL timespan.
This detail data is then processed to provide the user with
several views of the same data, with each view appearing in
the database at levels of summarization, starting with the
data organized and summarized by day of the month (DAYS),
then, week of the year (WEEKS), month of the year (MONTHS),
and, finally, by year (YEARS).
Consequently, the user is able to select the data that is
organized and summarized closest to the reporting
requirement, resulting in less programmer time and machine
resources consumed in satisfying the information request.
CA MICS' database organization facilitates both database
updating and retrieval. Issues of database backup, online
storage demands, frequency of data use, and requirements for
long-term retention of data introduce additional database
requirements that are satisfied through a multi-structure
implementation.
CA MICS DATA STRUCTURES
The database timespans are stored in four distinctly
different data structures: online, archive, backup, and
special.
Online Data Structure
The online structure provides the data nucleus for daily
updating, bringing the status of the online data current to
the previous day's activity, including week-to-date,
month-to-date, and year-to-date maintenance. The standard
Management Objective and Exception Reports are generated
directly, using the online data as input, resulting in an
efficient, quick, and mount-free process. The online data
may be accessed directly, through SAS or using the CA MICS
Information Center Facility, to satisfy a large majority of
short-term information requirements related to problem
tracking and diagnosis; short-term capacity planning; daily,
weekly, and monthly management and technical reporting;
standards and security analysis; etc.
Archive Data Structure
The archive structure provides a less expensive method
for retaining data for much longer retention periods than the
data maintained online. The archive provides the means for
retaining data for long-term capacity planning, forecasting,
growth analysis, and user workload auditing.
The archive data is organized into two groupings: audit
and history. Audit data is maintained for a select type of
data in order to establish an audit trail for "units of work"
as they were executed (e.g., TSO interactive programs, batch
jobs, etc.). History data is maintained for data that is
less frequently used as it ages, but is vital for longer term
analysis requirements. The archive data is to be stored on
magnetic tape or mass storage and should be retained for at
least one year.
Backup Data Structure
The backup structure provides a complete daily backup of
the data maintained online to ensure a fast, easy-to-use, and
total online database recovery.
It is recommended that the database be backed up daily
and stored on magnetic tape. The database can then be fully
or partially (by timespan) restored at any time.
Special Data Structure
The special structure provides the data nucleus for
satisfying the need for data not available in the online or
archive data structure. The update and use of the special
structure is completely separate from the other data
structures. You can create a special database with any data
you wish to use.
Figure 1-1a illustrates the relationship of the four data
structures comprising the total CA MICS Database capability.
Note: CA MICS employs additional data structures for
internal processes. For example, the optional incremental
update facility employs the Incremental Database structure to
support incremental updating of the Online Data Structure.
Another example is the Work File data structure employed to
support optional internal step restart. These internal
process data structures are not typically used in normal
CA MICS data retrieval and reporting, and are NOT discussed
in this manual. See the Planning, Installation, Operation
and Maintenance Guide for more information on internal
process data structures.
The following sections describe and illustrate the database
structure, organization, and use of the online, archive,
and special data structures. The backup data structure is an
image-copy of the online data as of the time that the last
BACKUP job was successfully completed. The backup data
structure is best understood by reviewing Section 4.8, BACKUP
Operational Job, in the CA MICS Planning, Installation,
Operation, and Maintenance Guide. Also review the actual
BACKUP job stream contained in the CA MICS control statement
library, prefix.MICS.CNTL, member BACKUP.
1 - Online Data Structure
2 - Archive Data Structure
3 - Special Data Structure
CA MICS DATABASE | +-----------------------------------------------------------------------------------------------+ | | | | +------------------------------+ +------------------------+ +------------------------------+ +------------------------------+ | ONLINE DATA | | ARCHIVE DATA | | BACKUP DATA | | SPECIAL DATABASE | +------------------------------+ +-----------+------------+ +------------------------------+ +------------------------------+ |DETAIL DAYS WEEKS MONTHS YEARS| | AUDIT | HISTORY | |DETAIL DAYS WEEKS MONTHS YEARS| |DETAIL DAYS WEEKS MONTHS YEARS| +------------------------------+ | DETAIL |WEEKS MONTHS| +------------------------------+ +------------------------------+ | +-----------+------------+ | | | | | | Storage: DASD Storage: Magnetic Tape Storage: Magnetic Tape Storage: DASD | | | | | | | | Processors: Processors: Processors: Processors: | | | | |-Standard Reports | |-Backup |-User written |-SAS/TSO SAS/GRAPH Inquiry |-User-Written Reports |-Restore | Reports |-Information Center Facility | | | |-User Written Reports | | | | | | | Primary Uses: Primary Uses: Primary Uses: Primary Uses: | | | | |-Problem Tracking |-Long-Term Capacity Planning |-Database Recovery |-Any analysis |-Basic Performance Management |-Growth Analysis | not possible |-Basic Capacity Planning |-Forecasting | with online or |-Standards Enforcement | | archive |-Security Violation Analysis |-User Workload Audit |-Workload Tracking and Control |-Installation Accounting
Figure 1-1a. Database Structure Overview
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |