Restarting an occurrence from the beginning

The LIST option of the modify current plan panel takes you to the MODIFYING OCCURRENCES IN THE CURRENT PLAN panel:

Figure 1. EQQMOCLL - Modifying occurrences in the current plan
EQQMOCLL --------- MODIFYING OCCURRENCES IN THE CURRENT PLAN   ROW 1 TO 4 OF 4
Command ===>                                                  Scroll ===> PAGE

Enter the CREATE command to add a new occurrence or
enter the GRAPH command to display occurrence list graphically or
enter any of the row commands below:
B - Browse, D - Delete, M - Modify, RG - Remove from group, DG - Delete Group,
C - Complete, W -Set to Waiting, R - Rerun, CG - Complete Group

Row Application                                 Input arrival   S   P  G  Add
cmd id                text                      date     time             func
'' CP                current plan              03/06/08 11.00  C   7  N
'' PAYBACKP          backup payroll database   03/06/08 12.00  W   5  N
'' PAYDAILY          daily payroll jobs        03/06/08 12.00  W   5  N
'' PAYW              weekly payroll jobs       03/06/09 14.00  W   5  Y  D
******************************* BOTTOM OF DATA ********************************
To restart an application occurrence from the beginning, enter W in the row command field for the occurrence. After you confirm the request, HCL Workload Automation for Z resets the status of all operations in the occurrence to W (waiting). All operations (whose predecessors have completed) are then automatically resubmitted if all other criteria for submission are fulfilled. In this process, all external and conditional successors that have a status of ready are reset to W (waiting) status. If they are conditional successors, the scheduler might reset the related conditions to undefined, meaning that:
  • Single dependencies in existing conditions are reset to undefined.
  • Each condition is reset to undefined depending on the specified rule.

If an external or conditional successor has started, however, the request to restart is rejected, and an error message is displayed. If this happens, consider deleting the external successor dependency and then reset the occurrence to waiting status. See Changing dependencies to an operation for details on how to delete dependencies.

Note: If you are using the advanced panels, you can rerun an occurrence from either the Table Row Commands panel (see EQQSRCLP - Table Row Commands panel) or from the Occurrence menu of the OPERATION IN THE CURRENT PLAN panel (see Occurrence).
If you want to reset the status of successors as well, you need RERUN instead of SET TO WAITING. See Rerunning an occurrence in the current plan from a specific operation.
Note:
  1. Row commands are usually executed immediately. Thus, if you cancel the rerun against which you have issued a NOP command, the operation remains removed (no-oped), because the NOP command has already been processed.
  2. If at some point an operation was set to HOLD or NOP, the HOLD or NOP status will stay in effect when the occurrence is set to waiting. To see which operations have been set to HOLD or NOP, request a list of the operations using option 5.3.
  3. You might need to HOLD or NOP operations that will be reset by the command.
  4. When an operation is rerun, HCL Workload Automation for Z uses the job that was last submitted for the operation.
  5. Same restrictions apply as for changing the operation status to ready by selecting option 6 (GENERAL) from the MODIFYING AN OPERATION IN THE CURRENT PLAN panel. In particular, a step or job restart request might imply a request to change to ready the status of an operation with conditional successors already started, completed, suppressed by condition, or ended in error. In this case the scheduler issues message EQQM208E. Only when rerunning an occurrence you might indirectly obtain this kind of change.