2. Planning for Installation and Use of CA MICS › 2.2 Preparing Your Site For CA MICS › 2.2.2 Resource Planning for CA MICS › 2.2.2.3 Tape Usage Requirements

2.2.2.3 Tape Usage Requirements

The number of tapes that are required for the normal
operation of CA MICS is a function of numerous user-supplied
parameters.  The CA MICS files stored on magnetic tape are:

    1 - Database Backup Files
    2 - Archive Audit Files
    3 - Archive Weekly History Files
    4 - Archive Monthly History Files
    5 - Optional Incremental Update Tape Database

Each of the above categories represents a number of tape
files organized as generation data groups and is stored with
multiple files on a single tape volume (e.g., all of the
backup files are stored on the same tape volume).  As a
general rule, assume that one tape will be required for each
generation data group that is defined for each of the
categories (for the number of GDG entries defined see section
2.3.3.2.1, JCL Option Definitions).

For example, specifying 53 GDG entries for the Archive Audit
Files, 10 entries for the Database Backup Files, 7 entries
for the Archive Weekly History Files, 5 entries for the
Archive Monthly History Files, and 10 entries for the monthly
backups will require a minimum of 85 tapes.  Additional tape
volumes will be required if you choose to exploit incremental
update facilities with the option of keeping the incremental
update database on tape between incremental update
executions.

The Archive Audit Files generally require 1 tape volume for
each generation and are created by the CA MICS WEEKLY job.

The Archive Weekly History Files normally require 1 to 2 tape
volumes per generation and are updated by the CA MICS WEEKLY
job.  Due to the cumulative nature of these files, they will
continue to grow in size (as you accumulate more data in the
CA MICS database) until they reach the CUTOFF size specified
by parameters in prefix.MICS.PARMS(DBMODEL).

The Archive Monthly History Files normally require 1 to 2
tape volumes per generation and are updated by the CA MICS
MONTHLY job.  Due to the cumulative nature of these files,
they will continue to grow in size (as you accumulate more
data in the CA MICS database) until they reach the CUTOFF
size specified by parameters in prefix.MICS.PARMS(DBMODEL).

The Database Backup Files generally require 1 tape volume per
generation and are created by the CA MICS BACKUP job, which
may be run daily, every other day, or weekly.  The Backup
files are also created by the MONTHLY job.  The size of the
files will increase as your CA MICS database fills up.

If activated, the optional incremental update tape database
feature generally requires 1 tape volume per generation for
each product for which you requested this option.

Accounting and Chargeback has additional tape requirements.
These are discussed in the Accounting and Chargeback User
Guide.

Use of individual product options and exits for storing
detail level transaction data files on tape will require
additional tape volumes.  See the individual product guides
for information on product specific tape usage.