6. DATA SOURCES › 6.1 Data Collection and Transport to CA MICS › 6.1.2 Data Volume Considerations

6.1.2 Data Volume Considerations

ACCOUNTING DATA VOLUMES

VMS ACCOUNTING is a fairly low-volume data source.  Records
are produced only when processes and images terminate, when a
LOGIN attempt fails, and when print jobs are processed.

Before enabling image-level accounting, you should consider
the expense required in disk space and processing time.
Image termination data can be useful for performance analysis
but should be collected only in sufficient quantity to serve
a specific purpose or study.  Also, you may choose to collect
image data for only certain image names through image install
options.  It is inadvisable to attempt full image-level
accounting or even selected image accounting on a widely used
image because the VMS overhead will be high.

If you choose to enable image-level accounting, review the
data element definitions for the DEAIMG file in
sharedprefix.MICS.GENLIB(DEXGENIN).  The CA MICS data element
IMGNAME is defined with a default length of 60 characters.
You may want to change this length based on your recording
requirements and the amount of database space needed to store
this field.  Refer to the CA MICS System Modification Guide
for more information on database tailoring and GENIN members.


MONITOR DATA VOLUMES

VMS MONITOR can be a high-volume data source depending on the
recording interval and the specific records that have been
enabled.  While an interval of 20 seconds may be useful for
specific performance studies, a more reasonable value for
historical data summarization and retention purposes should
be considered.  Too small an interval will actually generate
so much data as to make its use prohibitive.  We suggest you
start with a 10 or 15 minute interval (600 to 900 seconds)
when setting up data collection for CA MICS use. Once you
have been able to determine the affect of this setting on
data volume and data use, you can adjust the interval on the
data collector.

The following records are written once per interval:

   CLUSTER
   DECNET
   DLOCK
   FCP
   FILE SYSTEM CACHE
   IO
   LOCK
   MSCP SERVER
   PAGE
   POOL
   STATES
   SYSTEM
   TRANSACTION

The following records contain multiple segments and generate
multiple CA MICS records:

   DISK - One per each selected disk device per interval
   MODES - One per CPU per interval
   PROCESSES - One per process per interval
   RMS - One per file per interval
   SCS - One per node per interval
   VECTOR - One per CPU per interval


DEXSUS DATA VOLUMES

DEXSUS can be a high-volume data source depending on the
frequency of operation and the specific system usage
measurements that have been enabled.

The most voluminous part of this data source is the
measurement supplied by the ANALYZE/DISK utility.  This
measurement set contains one record for each file in each
directory on each disk included in the analysis.  This data
is the basis for the CA MICS DESDKU file and also supplies
some information for the DESDKD file.

By comparison, the other measurements recorded by the DEXSUS
routine account for a relatively small volume of data.