A backup mission backs up a group of reports for a specified number of days or generations. The workflow of a backup mission consists of the following stages:
The Control-V New Day procedure analyzes the basic scheduling criteria of the backup missions and decides which missions should be executed on the given day (for example, different backup procedures can be employed for end-of-month processing versus the regular working day). The missions are placed in the Active Missions file.
The monitor analyzes the mission’s runtime scheduling criteria (prerequisite conditions, time constraints, priority, and so on). If all scheduling criteria are met, the backup mission executes.
The backup mission scans the Active User Report List file for reports which should be backed up by the specified backup mission and have not been backed up yet. The name of the backup mission is specified in the report decollating parameters.
The backup mission prepares a list of datasets to be backed up. The list can be in one of the following formats:
DF/DSS
DF/HSM
FDR
DMS/OS
ASM2
ARCS
Site controlled format
Control is passed to either:
A job under the Control-M Production Control System
A job submitted by another production control system
A job submitted from the Control-D monitor
The job backs up all the files in the list in a fast and reliable manner since it employs the standard backup procedures used by the site.
After the job finishes executing, it notifies the Control-D monitor that the backup has successfully completed, and lists the tape numbers used in the backup process.
Optionally, the monitor adds and/or deletes requested prerequisite conditions and uses the Shout facility to notify appropriate personnel.
