Overview of the startover process


This section outlines the process performed when Execution starts over a worklist.

Warning

During startover processing, Execution makes no provisions for any reversal or recovery of processes that might have been already performed.

  1. Checks the status of the work ID.
  2. Executes the worklist from the beginning and establishes the runtime environment from the values in the worklist.
  3. Starts the first BMC utility in the worklist with the SSID, UTILID, NEW/RESTART parameters.

    Important

    Execution starts the BMC AMI Copy utility with the SSID, UTILID, NEW/RESET parameters, and the CHECK PLUS utility with the SSID, UTILID, NEW parameters.

    Important

    If the BMC or IBM utility encounters an existing UTILID or a UTILID that is associated with another utility on this object, the utility might terminate with an error. For example, if the first utility is REORG PLUS but the existing UTILID is associated with LOADPLUS, REORG PLUS might terminate with an error. You might need to terminate the utility or allow the utility to complete.

To start a worklist over, select the Build Startover JCL from previous execution JCL option on the Execution JCL Build Interface panel. When you select this option, the products insert the STARTOVER keyword into the AEXIN input stream.

If the worklist has been executed once and the DASD data sets exist, JCL Generation creates DD statements with a disposition of SHR. If the worklist has not been executed and the data sets do not exist, you must ensure that the DD statements are created with a disposition of (NEW, CATLG, CATLG). To do so, select Build Initial JCL from the Execution JCL Build Interface panel. Then, manually add the STARTOVER keyword to the AEXIN input stream.

If you want to start a worklist over at a new beginning, you can edit the worklist to remove unwanted commands and then select the Build Start Over JCL from previous execution JCL option to execute the modified worklist.

Warning

Exercise caution when editing the worklist to remove commands. If you remove the unload commands from a worklist before you generate JCL, the SYSRnnnn data sets are generated as DD DUMMY. You might need to generate the JCL first and then remove any unwanted commands.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*