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.2 DASD Space Requirements

2.2.2.2 DASD Space Requirements

The DASD space required to operate CA MICS on an ongoing
basis is a function of the following:

o   The number of installations and/or CPUs included in the
    CA MICS databases

o   The CA MICS products used

o   The volume of work processed in terms of number of users,
    commands, jobs, steps, online system transactions, etc.

o   The CA MICS database CYCLE retention levels

o   The use of SAS file compression

o   The number of account codes defined by user account code
    exits and account code timespan masking options

o   Database tailoring to drop measurements and metrics of
    lesser value to your installation

o   The use of the multiple work file, internal step restart,
    and incremental update features.

Remember to include the DASD space required for CA MICS
program, documentation, and control libraries when estimating
DASD space requirements.  Refer to section 3.2, "Load
Distribution Libraries", for information about CA MICS system
data sets.

CA MICS can use space in the Hierarchical File System.  The
CA MICS Platform requires at least 10 megabytes of space.
Additional space may be required for additional CA MICS DIAs,
and features.

SAS Data Libraries are DSORG=PS, which makes them eligible
for alteration by space management utilities that free up
unused space.  Allowing this to happen will cause frequent
system B37 abends.  You must explicitly exclude all SAS data
libraries used in CA MICS from these space management
programs.

To avoid problems, either allow adequate secondary space for
your CA MICS data files or exclude them from the utilities.