Previous Topic: 4.3.3.2.21 HISTM Operational JobNext Topic: 4.3.3.3 Job Steps

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

4.3.3.2.22 BACKUPM Operational Job

 +-----------------------------------------------------------+
 |                                                           |
 |                                  Checkpoint               |
 |            Online                  File                   |
 |           Database                   |                    |
 |               |                      |                    |
 |               +----------+-----------+                    |
 |                          |                                |
 |                          |                                |
 |                          V                                |
 |   Checkpoint        +---------+          Operational      |
 |      File<--------->| BACKUPM |--------->Status and       |
 |                     +---------+          Tracking         |
 |                          |                                |
 |                          |                                |
 |                          |                                |
 |                          V                                |
 |                       Backup                              |
 |                        Data                               |
 |                        Files                              |
 |                                                           |
 +-----------------------------------------------------------+
 
 When MONTHLY BACKUP YES is specified (also the default) in
 prefix.MICS.PARMS(JCLDEF), a monthly backup is set to be run
 after MONTHLY processing is done.  When AUTOSUBMIT YES is
 also specified in prefix.MICS.PARMS(JCLDEF), this backup is
 run as the stand-alone job BACKUPM.  The JCL for BACKUPM is
 in prefix.MICS.CNTL(BACKUPM).  It is tailored to the
 components in the unit.
 
 The BACKUPM 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 BACKUPM 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 BACKUPM job also backs up:
 
         sharedprefix.MICS.CAPACITY
 
 The BACKUPM 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 BACKUPM job malfunctions, no other update functions
 will be able to execute.  It must successfully complete
 before other functions can start.
 
 The BACKUPM job will not be able to execute if any of the
 latest DAILY, WEEKLY, MONTHLY, YEARLY, and RESTORE jobs have
 been completed unsuccessfully.  The BACKUPM job will be able
 to execute if a prior BACKUPM job failed -- that is, you can
 restart the BACKUP job by rerunning the BACKUPM job.