4. Operation › 4.3 Operations Reference › 4.3.4 Operational Status and Tracking › 4.3.4.3 CA MICS Operations

4.3.4.3 CA MICS Operations

CA MICS maintains a processing schedule based on the
specifications you entered in sharedprefix.MICS.PARMS
(defaults for all units) and in prefix.MICS.PARMS for each
unit database.  You specified backup frequency in
prefix.MICS.PARMS(JCLDEF) and indicated in
prefix.MICS.PARMS(EXECDEF) whether WEEKLY, MONTHLY, and/or
YEARLY processing can occur during weekends.  You also
defined your installation's calendar (e.g., a 13 month fiscal
calendar) and week (e.g., the week starts on Sunday vs.
Monday) through the sharedprefix.MICS.PARMS(CPLXDEF) or
prefix.MICS.PARMS(SITE) parameter members.

You can simply enter the SCHEDULE command to execute the
CA MICS processing scheduled for today (see the Current
Operation column).  You can scroll RIGHT on the Operational
Status and Tracking display to see the seven day CA MICS
processing schedule forecast.

You can also schedule CA MICS processing with specific
commands for the DAILY, WEEKLY, MONTHLY, and YEARLY
processing cycles.  Each of these options performs a DAILY
update and a database BACKUP.  The WEEKLY/MONTHLY/YEARLY
options follow the DAILY update with the requested
WEEKLY/MONTHLY/YEARLY close-out cycle and then the BACKUP.

It is always a good idea to back up the database before
making any changes.  You can enter the BACKUP command for a
special, ad hoc database backup.  You will be prompted to
provide a brief explanation of the purpose of the backup so
that CA MICS can label the backup cycle for reference should
you need to RESTORE.

Occasionally, problems occur in CA MICS processing.
Operational Status and Tracking presents information on
database update status and provides tools for restart and
recovery.  Use the RESTART command to restart CA MICS
processing.  If the failure occurred during the CA MICS aging
process, call CA MICS Product Support.

There will also be times where you will want to block
database update processing.  For example, you may need to
suspend Database updating while you apply selected PSP
maintenance.  Operational Status and Tracking provides the
SUSPEND command to block database update processing until you
are ready to continue with normal CA MICS operations.  The
RESUME command returns a unit database to a normal
operational state.

Operational Status and Tracking also simplifies special
recovery operations.  The FORCE command tells CA MICS to
select specific input data and/or accept input data which
would normally fail CA MICS date/time checks. For example, if
a tape of SMF data was missed, you can FORCE this missing
data into the database even though it pre-dates the most
recent CA MICS checkpoint dates.  You can even select the
missing data from a composite (e.g., week-to-date) input data
tape.

See the Operational Status and Tracking Commands section
(4.3.4.4) for more information on each command.