JOBA has a maxrun time of 240 min
JOBA failed after executing for 40 minute
JOBA Sits in failed status going past its overdue time and an alert is triggered.
Operations manually reset the overdue time in the CSF.
Job was resubmitted by operations
Job went overdue 40 minutes later, not waiting for the 240 minutes as coded in the maxruntime
Release : 12.0
Component : ESP WORKLOAD AUTOMATION
This caused Operations to follow a procedure for reaching the original MAXRUNTIME and forced completed job.
If the overdue time is manually changed to a time from CSF, using the RT command, this will super-speed the maxruntime as it relates to resubmission time. You would want to blank out the overdue time to nothing and a resubmission will set overdue based on MAXRUNTIME.