Backup Mission Workflow

The backup mission workflow of Control‑D is shown below. It illustrates the stages involved from initially scheduling the backup mission through backing up the CDAM datasets.

The following figure depicts the workflow of a backup mission:

Figure 56 Backup Mission Workflow

• The Active User Report List file is scanned by the Control‑D monitor for all reports requiring backup by the specified backup mission name. (This is a fast scan, not a scan of the entire file.) Reports that have been previously backed up, or have been restored from a backup, are not backed up a second time. The result of this process is a list of dataset names to be backed up.
• The Control‑D monitor reads a skeleton job from the library referenced by DD statement DADSKL of the Control‑D monitor. The member name must be the same as the backup mission name (for example, BKP0031D).

  Since the same library is used for printing, backup, restore and migration mission skeletons, the name of each mission must be unique.

  When you define a new backup mission, you must create a new skeleton job with the same name.

  The member must contain specific parameters that are interpreted by the Control‑D monitor. The following table describes these parameters.

  Table 162 Mandatory Parameters for Skeleton Member

  Parameter	Description
  %DSNS%	Resolves into a list of all the dataset names that have to be backed up. This list is in DF/DSS, DF/HSM, FDR, DMS/OS, ASM2 or ARCS format depending on installation parameters. Mandatory.
  %TIMESTMP%	Resolves into a timestamp that is later used by Control‑D for internal purposes. Mandatory.
  %MISSNAME%	Resolves into the backup mission name. Mandatory.
  %COND% condnm	When the preparation of the backup job is completed, the specified condition name is added to the IOA Conditions file. The ODAT of the condition is the original scheduling date of the backup mission. This can be used for triggering the backup job under Control‑M. Optional.
  %ODATE%	Resolves into Dyymmdd, where yymmdd represents the ODATE of the backup mission. Optional.
  %TIME%	Resolves into Thhmmss, where hhmmss represents the start time of the backup mission. Optional.
  %RETPD%	Resolves into nnnn, which represents the retention period of the produced backup data set according to the backup mission definition. Optional.
  %EXPDT%	Resolves into the expiration date for the produced backup data set, in yyyy/ddd format, according to the backup mission definition. Optional.

• When Control‑D finishes preparing the member for submission, control passes to Exit CTDX010. This exit can modify the contents of the submitted job by adding, deleting or modifying the JCL. For example, the dataset names list can have a format different from the DF/DSS, DF/HSM, FDR, DMS/OS, ASM2 or ARCS format. The exit can return the following return codes:

  Code	Description
  0	Submit the job.
  4	Do not submit the job (normally used when the submission is to be executed by a production control system).

  Instead of using exit CTDX010, you can define parameter BKPJOBST=N in CTDPARM, which means “Do not submit the job.”

  The member is written to the library referenced by DD statement DADJOB of the Control‑D monitor with a name identical to the name of the backup mission. Therefore, this library must be different from the library referenced by DD statement DADSKL. The return code from the user exit determines if the job is or is not submitted. If Control‑M is installed, submission of the job can be triggered by the %COND% statement. (The advantage of this method is that overall production tape workload and tape usage priority are taken into consideration when submitting the backup job.)

• The original member supplied contains the following:
  • the DF/DSS, DF/HSM, FDR, DMS/OS, ASM2 or ARCS backup utility

    Note: Control‑D cannot use the ARCS, DFDSS, or FDR utility to back up CDAM data sets on more than five tape volumes unless the backup data sets are cataloged.

  • a program that analyzes the output of the backup process and updates Control‑D files with the results (for example, the tape numbers used)
• When the job finishes executing, the Control‑D monitor is notified (by the second step) and the backup mission’s post‑processing parameters (OUT and SHOUT) are processed.