What is causing TRAC305A to occur after updating MONITORDELAY option in Jobtrac?
A change to the MONITORDELAY option will not result in TRAC305A message. This message normally occurs when the primary Jobtrac system has not cycled recently. Reasons that the primary system may have not cycled can be due to the fact that the log file may be spilling at the time, a large schedule may be processing in Jobtrac or possibly a data set might have a reserve issued against it hanging up Jobtrac.
As always, please contact CA Technologies support for CA Jobtrac Job Management if you have any further questions.