7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.3 Database Space Modeling (DBMODEL) › 7.3.3.1 Data Retention Specifications (FILE Statement)

7.3.3.1 Data Retention Specifications (FILE Statement)

This section describes cycle (data retention) definitions
required for the DB2 Analyzer, discusses how to determine the
DB2 data cycles required, and provides instructions for
completing the FILE statements in the PARMS member DBMODEL.

Database Data Retention Worksheet Definition
--------------------------------------------

Figure 7-4 provides a worksheet to define the different
retention limits for the online and archive database files.
The numbers shown on the worksheet reflect the default
retention values in prefix.MICS.PARMS(DBMODEL).

Use the worksheet to define your retention specifications,
which in turn will allow you to determine the appropriate
values for the modeling process.

Note that the DBMODEL worksheet shown here contains values
for this product only.  For more information, see Section
2.3.4.1, Preparing the Modeling Input, in the CA MICS PIOM
Guide.

The worksheet is organized by information area.  Each file in
the area is listed by name.  For each file, a line is
formatted to allow six definitions in the online database and
two in the archive database:

o The online database files quantify the number of cycles of
  data that will be maintained in the DETAIL, DAYS, WEEKS,
  MONTHS, and YEARS timespans and the TABLES data area.

o The two definitions for the archive database files quantify
  the number of cycles of data to be retained, up to the
  cutoff limit defined.  The archive definitions have no
  impact on the size of the database and may be specified
  whether or not the weekly and/or monthly archive history
  files have actually been activated (see Section 2.3.3,
  CA MICS JCL Planning and Parameters, of the PIOM).

The worksheet formats provide an underscored area for the
user's definition, followed by the recommended value, shown
within parentheses.  If the underscored area contains a value
of 00, the file is not supported for the indicated timespan.
To add support, you must perform database tailoring as
described in Section 6.2, Tailoring the Database, of the
System Modification Guide (SMG).

When specifying a retention limit, remember that the number
may never be zero if the file has been defined to be active
in the timespan.


DB2 Data Retention Definition
-----------------------------

The DB2 Analyzer is comprised of the DB2 Information Area and
its files.  The FILE statements shown below specify the
default online and archive history retention limits for each
file.  A complete description of the FILE statement is
provided in the PIOM, Section 2.3.4.1, Preparing the Modeling
Input.

 
                           +--------------------------------------------------------------------------+
                           | INSTALLATION PREPARATION WORKSHEET: Data Retention Specifications        |
                           |                                                                          |
                           | PARMS Library Member is DBMODEL                                          |
                           |                                                                          |
                           | Reference Sections: 7.3.3.1  CA MICS DB2 Analyzer Guide                  |
                           +------+-----------------------------------------------+-------------------+
                           |      |            Online Database Retention          |  Archive Cut-Off  |
                           | File |DETAIL    DAYS   WEEKS   MONTHS  YEARS  TABLES | WEEKS    MONTHS   |
                           | Name |                                               |                   |
                           +------+-----------------------------------------------+-------------------+
                           |DB2DSY| __(07)   __(33) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2_DS| __(01)   00(00) 00(00)  00(00)  0(0)   00(00) | 000(000) 000(000) |
                           |DB2DSD| __(07)   __(33) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2_DD| __(01)   00(00) 00(00)  00(00)  0(0)   00(00) | 000(000) 000(000) |
                           |DB2DSU| __(07)   __(33) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2DSP| __(07)   __(33) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2DDY| __(03)   __(15) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2_SH| __(01)   00(00) 00(00)  00(00)  0(0)   00(00) | 000(000) 000(000) |
                           |DB2DDP| __(03)   __(15) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2DDU| __(03)   __(15) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           |DB2DPP| __(07)   __(33) __(09)  __(06)  _(1)   00(00) | ___(053) ___(024) |
                           +------+-----------------------------------------------+-------------------+
                           | ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. |
                           +--------------------------------------------------------------------------+

 Figure 7-4.   Data Retention Specification Worksheet