Why is the Start Time changing on some In Progress Jobstream runs on the AAI Monitoring tab?
Release : 6.2.0
Component : AUTOMIC AUTOMATION INTELLIGENCE ENGINE
When a jobstream has a Max Jobstream Run Duration set, you may see the Start Time of in progress jobstreams change on the monitoring tab as the run gets closer to the to the target job and exceeds the Max Jobstream Run Duration.
For example, for a job stream with Max Duration set to 12 hours. At time 1, the JSR is predicted to finish at 20:00, and we set the start time of the JSR to the first job run within 12 hours ( which is at earlier to be 8:00), let's say that job starts at 8:10, then the JSR start time is set to 8:10. And it happens that 20:00 is later than the late time. Then we would send out Late Alert. At time 2, the JSR is delayed more because more jobs failed and restarted, it is now predicted to finish at 22:00, the first job run at time 1 is no longer within 12 hour duration, so it would not be included in the JSR any more, the new earliest job run within 12 hours started at 10:30, thus the JSR start time is set to 10:30. We would not see alert again at this time because the alert for this job stream was already sent out.
For more details about Maximum Jobstream Run Duration see here.
There may be s in which job s that take place sufficiently long before the ning of the Target Job can be ignored. Including these s may make for an unnecessarily complicated . In such cases, s can be excluded if they occurred early enough by setting this parameter. This parameter limits job s in a to those s within the given time preceding the end of a Target Job .imum (CA7/TES):
This can be set on a jobstream level for CA7 and Tidal schedulers.
For Autosys there is a server wide parameter set to 24 hours by default.