Processing Element Actions › Restore Statement › How Restore Processing Works

How Restore Processing Works

The processing sequence for the Restore action follows:

1. CA Endevor SCM determines whether the element is present in the stage indicated. If the element exists in that stage, the Restore action fails.
2. Restores the element, if it is not present, to the specified location (environment, stage, system, subsystem, and type). This includes:
   • Restoring all base and delta levels for the element.
   • Copying the element definition to the Master Control File.
   • Restoring component lists, if present.

   If you use the NEW VERSION option, CA Endevor SCM assigns the new version number to the restored element. Otherwise, the element retains its version number from the file.

3. Updates the Master Control File.
4. Continues based on the value in the BYPASS GENERATE PROCESSOR field. If the value in this field is Y, CA Endevor SCM does not generate the element.

   If the value in this field is N, CA Endevor SCM:

   • Determines the processor group to use. It then executes the generate processor in that group if one has been specified.

     Note: If you are performing multiple element restores, all of the elements will be restored before the generate processors are executed.

   • Reads the type definition for a source output library specification, then writes a copy of the current level of the element to that library. If EXPAND INCLUDES = Y, Endevor expands INCLUDE statements in the source. After the generate processor has been run for the element, Endevor updates the information in the Master Control File.
5. Updates the Master Control File after the RESTORE action is successfully completed.