Defining Additional Backup/Restore Missions

When Control-D is installed, a number of commonly-used backup and restore missions are supplied. Following is a list of these missions:

Table 5 Commonly Used Backup and Restore Missions

In most cases, the supplied missions meet the requirements of your data center.

If you want to define additional backup and/or restore missions, use the CLIST CTDCRMIS. This CLIST accepts essential information concerning the requested mission and builds all required components for the mission. The required components built by the CLIST are:

• Backup or restore mission definition in the BKPMIS or RSTMIS libraries. This definition contains identifying information, scheduling criteria, number of days to keep (for backup missions), run interval (for restore missions), and so on.
• JCL skeleton in the Control-D SKL library. This skeleton is used to build backup and restore jobs in conjunction with the backup and restore utility for a site (specified during the installation process).

After activating the CLIST, all required components are created, and the mission can be activated.

To set up the mission for automatic ordering, refer to Setting Up Automatic Orders of Missions.

While processing a backup and/or a restore mission, Control-D creates the JCL required for the backup or restore job. The skeleton of the JCL resides in the Control-D SKL library. The JCL created for each backup or restore mission is stored in the Control-D JOB library. It is important to compress the Control-D JOB library periodically, preferably daily.