4. Operation › 4.3 Operations Reference › 4.3.3 Operational Processes, Jobs, and Steps › 4.3.3.2 Operational Jobs › 4.3.3.2.5 BACKUP Operational Job

4.3.3.2.5 BACKUP Operational Job

+-----------------------------------------------------------+
|                                                           |
|                                  Checkpoint               |
|            Online                  File                   |
|           Database                   |                    |
|               |                      |                    |
|               +----------+-----------+                    |
|                          |                                |
|                          |                                |
|                          V                                |
|   Checkpoint        +---------+          Operational      |
|      File<--------->| BACKUP  |--------->Status and       |
|                     +---------+          Tracking         |
|                          |                                |
|                          |                                |
|                          |                                |
|                          V                                |
|                       Backup                              |
|                        Data                               |
|                        Files                              |
|                                                           |
+-----------------------------------------------------------+

The BACKUP job runs after the last update job completes
successfully.  BACKUP frequency (daily, bi-daily, or weekly)
is specified in prefix.MICS.PARMS(JCLDEF).

The JCL for the BACKUP job is in prefix.MICS.CNTL(BACKUP).
It is tailored to the components in the unit.

The BACKUP job creates a copy of the Database in six
generation data groups, named:

        tapeprefix.MICS.BACKUP.CHECKPT
        tapeprefix.MICS.BACKUP.DETAIL
        tapeprefix.MICS.BACKUP.DAYS
        tapeprefix.MICS.BACKUP.WEEKS
        tapeprefix.MICS.BACKUP.MONTHS
        tapeprefix.MICS.BACKUP.YEARS

The BACKUP job for the PRIMARY unit database also backs up:

        sharedprefix.MICS.SCREENS
        sharedprefix.MICS.TABLES
        sharedprefix.MICS.ISPTLIB

If the CA MICS Capacity Planner is installed in the PRIMARY
unit, the PRIMARY unit BACKUP job also backs up:

        sharedprefix.MICS.CAPACITY

The BACKUP job tracks compressed data on an inventory so that
compressed data can be restored in compressed mode.  (The SAS
System is not directed to write compressed data to tape in
compressed mode.)

DEPENDENCIES

If the BACKUP job malfunctions, no other update functions
will be able to execute.  The BACKUP job must successfully
complete before other functions can start.

The BACKUP job will not be able to execute if any of the
latest DAILY, WEEKLY, MONTHLY, YEARLY, and RESTORE jobs have
been completed unsuccessfully.  The BACKUP job will be able
to execute if a prior BACKUP job failed -- that is, you can
restart the BACKUP job by rerunning the BACKUP job.