Previous Topic: 5. FILES

Next Topic: 5.2 DB2 System Activity (DB2DSY) File

5.1 Introduction


The database is physically organized using the extensive
SAS database management facilities.   The resulting database
design consists of a related network of small, segmented SAS
files providing standard physical access to selected portions
of the stored data as well as the ability for relational data
retrieval.  The major features of the database include:

o  A single, common method for storing and retrieving
   different data sources (for example, CA TSO/MON PM, RMF).

o  Multi-level data summarization capability to maintain data
   at the detail level as well as summarization to the daily,
   weekly, monthly, and yearly levels.

o  Multi-level database storage providing for online, archive
   (offline), and backup storage of the data base.

o  Efficient processing of large volumes of measurement data
   to allow update of the database from multiple data
   sources.

o  Common online inquiry and batch reporting facilities to
   access all data areas of the database.

o  Segmentation of data into small, related SAS files that
   minimize the amount of data to be traversed for the
   majority of inquiry/reporting requirements.

o  Data integrity validation to ensure the accuracy and
   completeness of data maintained.

o  Backup/recovery facilities to enable restoration of part
   or all of the database.

o  Special processing facilities to allow access to
   information not available in the standard online and
   offline database.

The database contains a number of features designed to
maximize your capability to quickly and easily use the
organized information.  These include:

o  Dictionary definitions that allow you to reference data
   elements without first having to define their format. You
   need not be concerned about data element attributes, which
   saves valuable time in inquiry and program definition.

o  Standardized file definitions that provide common
   definitions for files in terms of data element labels,
   content and format, regardless of where a particular file
   may reside in the database. The file definition for TSO
   system activity is always the same, regardless of whether
   the request is for Detail, Daily or Monthly timespan
   level.

o  Common retrieval keys are defined in all files to simplify
   your selection, merging and data manipulation operations.
   These common keys include such standard elements as system
   identification, date/time stamps, date, time, hour, day,
   zone, and userids. This common key provision allows you to
   easily integrate unlike data sources (for example, CA
   TSO/MON PM and RMF).

o  Derived data elements (for example, average response time)
   are precalculated and maintained in the database to
   minimize your access time to frequently-used elements.

o  Data values are carried in decoded form (for example,
   device type is 3350) rather than the typical encoded
   pattern (for example, X'80') to improve data usability and
   reduce the required analysis time.