1. Database Structure › 1.2 Database Structure and Organization › 1.2.2 Archive Data Structure › 1.2.2.2 Archive History Data
1.2.2.2 Archive History Data
The Archived History Data is comprised of weekly and monthly
master data sets, which contain the historical data for
periods in excess of the online data retention limits. The
archive history data is maintained so that there is a
corresponding archive File for each File defined in the WEEKS
and MONTHS Timespans online.
Figure 1-11 illustrates the update process performed with
each File in the online WEEKS Timespan on a weekly basis.
The activity from the previous week is read along with the
cumulative weekly activity maintained in the archive data set
(GDG level 0). The File representing last week's activity
and the File containing the archive weeks history are input,
interleaved, and output to create a new archive weeks history
File (GDG data set level +1). Data that is older than the
archive cut-off date is not output to the new archive weeks
history File.
+-----------------------------------------------------------+
| Last Week's Activity Archive Week's Activity |
| |
| _diiiW..iiifff01 MICS.HISTW.iiifff(0) < - + |
| | | | |
| +---------------------------+ |
| | | |
| Weekly Archive |
| Update | |
| | |
| v | |
| MICS.HISTW.iiifff(+1) - - - - - - > + |
| |
+-----------------------------------------------------------+
Figure 1-11. Archive Weekly Update Process
This archive process results in a single OS/390 GDG for each
online defined File. The File is not broken up into Cycles
as is the case with the online Files, and may be processed
quite easily. By referencing the File's archive data set
name and the SAS File name within the program, the entire
history of a given File is retrievable.
The Files included in the archive weekly data if the
default definitions are used include:
tapeprefix.MICS.HISTW.iiifff: These data sets contain the
archived historical data for the WEEKS Timespan created on a
weekly basis. The 'iiifff' part of each generation data
group identifies the specific OS/390 data set that
corresponds to the database File in the WEEKS Timespan that
was archived. There is one GDG for each database File in the
WEEKS Timespan. For specific file names, refer to Chapter 5,
"Files", of each product's guide.
Figure 1-12 illustrates the update process performed with
each File in the online MONTHS Timespan on a monthly basis.
The activity from the previous month is read along with the
cumulative monthly activity maintained in the archive data
set (GDG level 0). The File representing last month's
activity and the File containing the archive months history
are input, interleaved, and output to create a new archive
months history File (GDG data set level +1). Data that is
older than the archive cut-off date is not output to the new
archive months history File.
+-----------------------------------------------------------+
| Last Month's Activity Archive Month's Activity |
| |
| _diiiM..iiifff01 MICS.HISTM.iiifff(0) < - + |
| | | | |
| +---------------------------+ |
| | | |
| Monthly Archive |
| Update | |
| | |
| v | |
| MICS.HISTM.iiifff(+1) - - - - - - > + |
| |
+-----------------------------------------------------------+
Figure 1-12. Archive Monthly Update Process
This archive process results in a single OS/390 GDG for each
online defined File. The File is not broken up into Cycles
as is the case with the online Files, and may be processed
quite easily. By referencing the File's archive data set
name and the SAS File name within the program, the entire
history of a given File is retrievable.
The Files included in the archive monthly data include:
tapeprefix.MICS.HISTM.iiifff: These data sets contain the
archived historical data for the MONTHS Timespan created on a
monthly basis. The 'iiifff' part of each generation data
group identifies the specific OS/390 data set that
corresponds to the database File in the MONTHS Timespan that
was archived. There is one GDG for each database File in the
MONTHS Timespan. For specific file names, refer to Chapter
5, "Files", of each product's guide.
The accessing of a SAS file on tape is handled no differently
than one on a disk, except for the JCL. The DD statement in
the JCL simply points to the archive data set name, which has
been cataloged as a tape data set. The processing
restriction is that the user may access only one file at a
time on the tape data set.
