Restore Mission Workflow

The following figure illustrates the restore mission workflow of Control‑D. It shows the stages involved from initially scheduling the restore mission through restoring the CDAM or Index datasets.

Figure 57 Restore Mission Workflow

The workflow of a restore mission is as follows:

• Restore is requested by online users through option R of the History or Migrated Report List screen. The History or Migrated User Report List file is scanned by the Control‑D monitor for all reports that need to be restored by the specified restore mission name. (This is a fast scan, not a scan of the entire file.) The result of this process is a list of dataset names to be restored.
• 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 restore mission name (for example, RST0060M).

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

  When you define a new restore mission, you must create a new skeleton job with the same name. The member must contain certain parameters that are interpreted by the Control‑D monitor. The parameters are listed in the table below.

  Table 165 Parameters for New Restore Mission Skeleton Job

  Parameter	Description
  %REPEAT% %ENDREPEAT%	Beginning and end of a repeating step. Mandatory. Since outputs can be backed up on many volumes, it is sometimes necessary (with certain archiving products) to perform the restore by more than one step. The definition of this repeating step is found between the %REPEAT% and %ENDREPEAT% statements (not applicable to DF/HSM, DMS/OS, ASM2 or ARCS formats).
  %DSNS%	Resolves into a list of all the dataset names that have to be restored. This list is in DF/DSS, DF/HSM, FDR, DMS/OS, ASM2, or ARCS format, depending on installation parameters. Mandatory.
  %VOLUMES%	Resolves into the volume serial numbers of the tapes taking part in the restore. (Applies to DF/DSS or FDR formats.) Mandatory when non-cataloged backup data sets are used. Not recommended when backup data sets are cataloged.
  %TIMESTMP%	Resolves into a timestamp that is later used by Control‑D for internal purposes. Mandatory.
  %MISSNAME%	Resolves into the restore mission name. Mandatory.
  %COND% cond‑name	When the preparation of the restore job has been completed, the specified condition name is added to the IOA Conditions file. The ODAT of the condition is identical to the original scheduling date of the restore mission. This can be used for triggering the restore job under Control‑M. Optional.
  %BKPUTIL%	Resolves to the backup utility name. Optional. The value of this parameter is determined as follows: The value of BKPUTIL in the skeleton is assigned as the utility name. For example, BKPUTIL=HSM. If BKPUTIL is not set in the skeleton member, the Backup utility name is taken from the BKPUTIL installation parameter in the CTDPARM member of the IOA PARM library, or When restoring migrated reports, the Backup utility name is CTVMIG.
  	In all the sample skeleton members provided in the Control‑D SKL library, the appropriate backup utility name is already assigned to parameter BKPUTIL. For details about how to use this parameter, see Restoring With the Original Backup Utility.
  %MEDIANAME%	This parameter is used only in the skeleton restoring migrated reports. Resolves into the name of the media to which the reports are migrated. If reports to be restored have been migrated to different media, several Restore steps with different media names will be created in the job.
  %ODATE%	Resolves into Dyymmdd, where yymmdd represents the ODATE of the backup mission that backed up the report. Optional.
  %TIME%	Resolves into Thhmmss, where hhmmss represents the start time of the backup mission that backed up the report. Optional.
  %DUMMY%	Intended for Control‑D internal use. Do not change.
  %ANALYZE%	Intended for Control‑D internal use. Do not change.

• When Control‑D finishes preparing the member for submission, control is passed to User Exit CTDX011. 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:

  Table 166 Return Codes for Exit CTDX011

  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 CTDX011, you can define parameter RSTJOBST=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 restore mission. Therefore, this library must be different from the library referenced by DD statement DADSKL. Depending on the return codes from the user exit, 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 is that overall production tape workload and tape usage priority are taken into consideration when submitting the restore job.)

  The original member supplied is divided into

  • the DF/DSS, DF/HSM, FDR, DMS/OS, ASM2 or ARCS restore utility or CTVUMG utility by restoring migrated reports.

    A step is created for each group of tapes (volsers) containing reports to be restored (not with all products). By restoring migrated reports, a step is created for each migration media.

  • a program that analyzes the output of the restore process and updates Control‑D with the results

    This step copies the restored user and report entries from the History or Migrated User Report List file to the Active User Report List file and indicates that a restore has been performed.

• If a CDAM or Index file to be restored already exists on disk, that file is not restored to disk. If all the files to be restored already exist on disk, the restore mission creates a restore job that performs only the ANALYZE step. This step copies user and sysdata records from the History or Migrated User Report List file to the Active User file and ends OK.
• When the job finishes executing, the Control‑D monitor is notified (by the second step) and the restore mission’s post‑processing parameters (OUT and SHOUT) are processed.