3. Maintenance Policies and Procedures › 3.2 User Maintenance Procedures › 3.2.3 Change Control Test Database › 3.2.3.1 Purpose

3.2.3.1 Purpose

The TEST database unit exists to test modifications to
CA MICS before such modifications are put into production.
That is the sole purpose for which this type of database unit
is designed.

The TEST database unit is fully capable of running in a
production mode.  Production processing is NOT the purpose of
a TEST database unit, but the ability to operate in such a
mode is necessary to provide comprehensive testing
facilities.

The TEST database unit has full database functions.  If
generated, all timespans are maintained.  Modifications to
any file in any timespan can be tested, printed, deleted, and
retested without affecting any other database unit.

All archiving functions are supported.  The effect of
enabling or disabling file audit or history archiving can be
quickly and easily tested, using manufactured data or data
copied from any other database unit.

Disjoint source files are maintained.  Modifications that
must be made to complex-level source files may be tested on
the TEST database unit without affecting any other database
unit or the target complex libraries.  The following special
libraries exist for that purpose, and are concatenated in
front of their complex-level counterparts for testing in the
TEST unit:

    sharedprefix.MICS.TEST.INCLLIB
    sharedprefix.MICS.TEST.LOAD
    sharedprefix.MICS.TEST.SOURCE

Another advantage of the TEST database unit is that, if it is
used properly (not in production), it can be deleted during
periods of no modification activity, and can be reinstalled
when needed.