Previous Topic: 4.3.3.1 Operational ProcessesNext 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  - (Optional)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 - (Optional) 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).
 
 o  BACKUPM  - Run once each month after the MONTHLY job to
               generate a tape backup of the entire Database.
               The monthly backup is run as this BACKUPM job
               when AUTOSUBMIT YES has been specified in
               prefix.MICS.PARMS(JCLDEF).
 
 The operational jobs are documented in the sections that
 follow.