Double launches of tasks at the same scheduled time after modification of the original launch

Products

• CA Automic Dollar Universe

Issue/Introduction

You have some scheduled tasks that have an Explicit Launch Date or Launch Window and Rule that were correctly scheduled in the future and their Launches seen in Launch Wait with a given numlanc/numsess.

Your Operators, for some reason:

• disable/enable that Launch 
• update its Launch Window
• modify some of the parameters of the launch

As a consequence, when you disable/enable the Task or Update the Task, a new Launch with the same scheduled time indicated in the Task will be generated if it's in the future with a numlanc/numsess superior.

The previously modified Launch of the task will also remain scheduled with the Launch Window that the operators had given.

Example of this situation, the task, session, uproc and MU are both the same, so is the Start/End Date of the Launch and its Processing Date:

Is this normal behavior?

How can we identify launches created by the Calculator and launches detached to the task due to the Operators modification?

Environment

Dollar Universe 6.x and 7.x

Cause

Expected behavior, this is decribed in the documentation here:

If the launch posted by the calculator is manually updated, it will not be erased.

Resolution

Here it is the way to differenciate two lines from the u_fmsb60.dta file (launches), one generated by the Calculator and one being a modifiied launch detached to the task caused by an Operator modification of the original launch.

Let's take the example before:

1. Retrieve the lines from u_fmsb60.dta containing the Launch Nº/numlanc which is in the position 47 and the Session Nº which is in the position 78, you can do this with a simple grep command such as:
   grep 4801658 u_fmsb60.dta | grep 4088608 and grep 4930390 u_fmsb60.dta | grep 4131527
   
   
   
2. Paste these lines from u_fmsb60.dta as above into Notepad++.
3. Now, we should have a look at position 122 where a "D" marks a launch created from a scheduled task and a "P" marks a launch created "manually" (detached to the task due to the Operators action).
   
   
   
4. We should also consider the difference at pos 242 ["O"/"0"], where the zero is set by the Calculator: the zero can be seen as a confirmation that the "D" record is created by the task scheduling and that the "P" record is not.

Additional Information

The correct action to fix this if you want to avoid the double launch consists on:

1. Disable the affected task:  the launch generated by the Calculator will be deleted and the "modified by Operators" launch will remain visible in Job Runs

2. Delete the "manually generated" launch that remained in Job Runs related to the task

3. Enable the affected task again: a new launch will be generated by the Calculator

Please reach out to Technical Support if you have doubts to identify / fix this double launches mentioning this Article.