We faced an "issue" in one of our application in DE series, where the jobs are triggering and being assigned an 'overdue' value even when the definition itself has no information for overdue time. We have checked all the dependent jobs as well and could not find any overdue time specified in any of those. Kindly let us know what could be the reason and how can we rectify the issue?
The jobs in the application is going overdue, since the “Propagate dueout time” attribute is enabled in the Application. The server sets the due out times of predecessors based on historical average elapsed times (a job's execution time averaged over previous runs). The calculation is using the run-times of the previous executions.
This can be rectify by modifying “Propagate dueout time” option in application level. Steps to be followed are given below:
1. Open the Application in the Define perspective:
The Application appears in the work space.
2. Right-click the Application in the Application Work-space view, and select Properties from the pop-up menu:
The Basic page of the Application properties dialog opens.
3. De-Select the Propagate dueout time check box and click OK:
The server disables anticipated end times and critical path analysis and propagates dueout times in the Application.
Ø If you want this option to apply to all Applications that you define, from the main menu click Window, Preferences, Desktop Client, Define Perspective, Application defaults, and select/de-select the Propagate dueout times check box.
Ø The below link provide more information on propagates dueout times:
Release: DSWAHA01300-12-Workload Automation DE-High Availability