4. Operation › 4.1 Overview › 4.1.3 Processing Schedule

4.1.3 Processing Schedule

The CA MICS Database must be updated on a timely and
progressive basis to ensure complete and accurate data.  A
processing schedule is required to ensure that the
appropriate operational processes take place.  The schedule
establishes that the jobs that make up these processes occur
on a daily, weekly, monthly, and yearly basis.

o  Execute the DAILY process each day (except when the
   WEEKLY, MONTHLY, or YEARLY process is scheduled--WEEKLY,
   MONTHLY, and YEARLY include DAILY).

   You may also choose to enable incremental update for one
   or more products, in which case you might execute the
   SPLITSMF and/or INCRccc jobs (by product) at scheduled
   points during the day, and then run the DAILY process at
   night for end-of-day close-out and reporting.

   NOTE:  You can optionally offload DAILY reporting to the
          stand-alone DAILYRPT job, thereby reducing DAILY
          job elapsed time and increasing database
          availability.  You can use the CA MICS AUTOSUBMIT
          option to automatically submit the DAILYRPT job, or
          you can schedule daily reporting externally.

o  Execute the WEEKLY process at the beginning of each new
   week (the WEEKLY process is composed of the DAILY,
   WEEKLY, and BACKUP operational jobs).

   NOTE:  You can optionally offload WEEKLY reporting to the
          stand-alone WEEKRPT job, Archive Audit tape
          processing to the stand-alone AUDIT job, and/or
          Archive Weekly History processing to the
          stand-alone HISTW job, thereby reducing WEEKLY job
          elapsed time and increasing database availability.
          You can use CA MICS AUTOSUBMIT options to
          automatically submit the WEEKRPT, AUDIT, and/or
          HISTW jobs, or you can schedule weekly reporting
          and/or weekly archive processing externally.

o  Execute the MONTHLY process at the beginning of each new
   month (the MONTHLY process is composed of the DAILY,
   MONTHLY, and BACKUP operational jobs).

   NOTE:  You can optionally offload MONTHLY reporting to the
          stand-alone MONTHRPT job, and/or Archive Monthly
          History processing to the stand-alone HISTM job,
          thereby reducing MONTHLY job elapsed time and
          increasing database availability.  You can use
          CA MICS AUTOSUBMIT options to automatically submit
          the MONTHRPT and/or HISTM jobs, or you can schedule
          monthly reporting and/or weekly archive processing
          externally.

o  Execute the YEARLY process at the beginning of each new
   year (the YEARLY process is composed of the DAILY,
   YEARLY, and BACKUP operational jobs).

You can define the CA MICS processing schedule to your
installation's production scheduling facility or you can use
standard CA MICS facilities to schedule production work.

CA MICS provides an online facility, Operational Status and
Tracking, that determines which operational process (DAILY,
WEEKLY, MONTHLY or YEARLY) needs to be performed.  You can
use the facility to generate and submit a tailored job stream
to accomplish the required operational process or you can use
it to monitor performance of your installation's production
scheduling facility.

If your installation does not have a production scheduling
facility AND you do not want to use online Operational Status
and Tracking for production process scheduling, then CA MICS
provides a job (SCHEDULE) that also determines which
operational process needs to be performed and builds a
tailored job stream to accomplish the process.  You can
submit the SCHEDULE job manually or run SCHEDULE under the
control of a production job scheduler.