2. USAGE GUIDELINES › 2.3 Miscellaneous Usage Notes for All Files › 2.3.3 Detail and Summary Data Considerations

2.3.3 Detail and Summary Data Considerations

In general, files in the DETAIL timespan will contain some
identifying name such as data set name (DSNAME). As these
observations are summarized, the identifying name at the
detail level is discarded, numeric data elements such as
tracks allocated (DAASPACA) are accumulated, and a new
observation is written into the summary level timespan.  The
values of the sort/sequence variables determine the
granularity (how many observations) at the new timespan.

Thus, at the DAYS, WEEKS, MONTHS, and YEARS timespans the
CA MICS Space Analyzer will store observations with an
accumulation of numeric values. You should know how to adjust
these summed variables by the appropriate factors to
interpret an average quantity.  Let's use the HSMMIG file as
an example to make this point more clear.

DETAIL Timespan
----------------

DSNAME             STORMGTC HSMACT1 HSMACT2 MIGALLSP MIGDSNNO
------------------ -------- ------- ------- -------- --------
MVS370.SP13.MACLIB STANDARD MIS-DIV SYSPROG    9.2       1
MVS370.SP13.MODGEN STANDARD MIS-DIV SYSPROG   20.4       1
MVS370.SP13.SMPMTS STANDARD MIS-DIV SYSPROG   10.4       1
MVS370.SP13.SMPSTS STANDARD MIS-DIV SYSPROG   15.6       1
MVS370.SP13.SMPPTS STANDARD MIS-DIV SYSPROG   25.8       1


DAYS Timespan
----------------

STORMGTC HSMACT1 HSMACT2 MIGALLSP MIGDSNNO
-------- ------- ------- -------- --------
STANDARD MIS-DIV SYSPROG   81.4       5

Note how DSNAME has been discarded and the commonality of the
sort/sequence variables has been used to determine the
observation that was created.  In this highly simplistic
example, our inventory has shown these 5 old data sets for an
obsolete release of MVS that are stored on tape controlled by
DFHSM.  In the DAYS timespan, we have stored the sum of the
values of MIGALLSP (allocated space in megabytes) and the
number of data sets represented in the observation
(MIGDSNNO).

Assuming no HRECALL or HDELETE activity is directed against
these data sets, they will be detected by the next inventory
run and a new cycle in the DAYS timespan will be created
with similar (if not identical) values.

Chapter 5 discusses each file structure in detail.