Previous Topic: 4.3.3.1 Operational Processes

Next Topic: 4.3.3.2.1 DAILY Operational Job

4.3.3.2 Operational Jobs


CA MICS provides standard operational jobs for updating,
reporting, maintaining, and recovering its Database:

o  DAILY    - run each day to update the DETAIL and DAYS
              timespan files plus week-to-date and month-
              to-date files in the WEEKS and MONTHS timespans
              (may be supplemented by one or more INCRccc job
              executions)

o  WEEKLY   - run once each week after the DAILY job for
              WEEKS timespan cycle close-out, weekly archive
              audit, and weekly archive history processing

o  MONTHLY  - run once each month after the DAILY job for
              MONTHS timespan cycle close-out and monthly
              archive history processing and for updating
              year-to-date files

o  YEARLY   - run once each year after the MONTHLY job for
              YEARS timespan cycle close-out

o  BACKUP   - run daily, bi-daily, or weekly (per user-
              specified backup frequency) to generate a tape
              backup of the entire Database

o  SCHEDULE - run each day to submit scheduled processing

o  RESTORE  - run whenever the database is damaged or must be
              recovered

o  DAILYRPT - run after DAILY to produce daily production
              reports

o  WEEKRPT  - run after WEEKLY to produce weekly production
              reports

o  MONTHRPT - run after MONTHLY to produce monthly production
              reports

o  RSTRTBLS - run to restore the TABLES and SCREENS data sets

o  RSTRTLIB - run to restore ISPF-based information

o  DAYSMFR  - run as necessary to recreate DAILY job work
              files

o  ACTDAY1R - run as necessary to restore the CA MICS
              Accounting and Chargeback DAY1 audit file

o  RSTATUS  - run as necessary to update Operational Status
              and Tracking control tables or to replace a
              lost Run Status Report

o  INCRccc  - optionally run one or more times per day to
              process a portion of the daily input data for
              the ccc data integration product to update the
              product's incremental update ("today to-date")
              DETAIL and DAYS timespan files

o  SPLITSMF - (optional) run one or more times a day to split
              the SMF input data into multiple files for
              processing in the INCRccc jobs.  SPLITSMF is a
              stand-alone version of the DAILY job's DAYSMF
              step and applies only to those products which
              take their input from the SMF files, and which
              are marked as INCRUPDATE YES and INCRSPLIT USE
              in prefix.MICS.PARMS(cccOPS).

o  IUDBINIT - optionally run to re-initialize in-progress
              incremental update processing after restoring
              the unit database files (i.e., after running
              the RESTORE job).  Messages in the RESTORE job
              MICSLOG will prompt you to execute IUDBINIT
              when needed.

o  AUDIT    - (optional) run after WEEKLY to perform optional
              Archive Audit processing.  The AUDIT job is
              used when you specify

                   ARCHIVE AUDIT YES JOB

              in prefix.MICS.PARMS(JCLDEF).

              NOTE:  You can execute AUDIT more frequently
                     (e.g., twice a week or daily) if DASD
                     space is inadequate for retaining
                     sufficient DETAIL/DAYS cycles for weekly
                     audit tape creation.

                     In this case, it is necessary to add the
                     following to prefix.MICS.PARMS(EXECDEF)

                          USERDEF AUDITCWK YES

                     This parameter overrides the default
                     audit archive processing.  Data for the
                     current week is retained and copied to
                     the new audit archive tape cycle.

o  HISTW    - (optional) run after WEEKLY to perform optional
              Archive Weekly History processing.  The HISTW
              job is used when you specify

                   ARCHIVE HISTW YES JOB

              in prefix.MICS.PARMS(JCLDEF).

o  HISTM    - (optional) run after MONTHLY to perform
              optional Archive Monthly History processing.
              The HISTM job is used when you specify

                   ARCHIVE HISTM YES JOB

              in prefix.MICS.PARMS(JCLDEF).

The operational jobs are documented in the sections that
follow.