2. Planning for Installation and Use of CA MICS › 2.3 Installation Planning and Parameter Specification › 2.3.4 Database Space Modeling Facility › 2.3.4.2 Executing the Database Space Modeling Facility

2.3.4.2 Executing the Database Space Modeling Facility

Two of the jobs provided in the control statement library,
prefix.MICS.CNTL, are:

DBSIZE   - Database Space Estimation
CYCLEGEN - Database Cycle Generation

After the DBMODEL member in prefix.MICS.PARMS has been
updated using FILE statement worksheets, the Database Space
Modeling Facility may be executed by submitting the DBSIZE
job, as shown below:

SUB 'prefix.MICS.CNTL(DBSIZE)'

This job needs input data of about one day to estimate the
required space to allocate on disk.  If some input data
cannot be provided, the space estimation will be less
accurate.

DBSIZE produces three reports, the Database Space Estimator
Libname Summary, Information Area Summary, and File Summary.
The Libname Summary shows the space allocation of the
physical data sets comprising the database.  For new
databases, the number of tracks shown in the Projected Space
column should be taken as the primary allocation for the
ALLOCATE job, together with a safe secondary allocation.

Once the analysis determines a database space estimate in
line with the data retention requirements and DASD space
available, then execute CYCLEGEN.

DBSIZE can also be used to estimate database size after
configuration changes, like adding a component to a unit.
Since, in this case, the new configuration must be generated
before DBSIZE can run, the existing DAILY job may be
affected. If the DAILY job has additional data integration
steps generated, SYSPARM='NODATA' should be coded on the EXEC
JCL card for the corresponding step until you are ready to
provide the new data and run it into the database.  For
example, if you have generated a database unit to contain
TSO, RMF, and SMF data and you don't have TSO data available,
the EXEC JCL card for the TSO step should look like:

//DAY010 EXEC MICSDBx,SYSPARM='NODATA'

where MICSDBx is the name of the procedure in the jobstream.