Hi,
Here is a very important information about usage of Cyclic job.
Example:
Imaging you have a cyclic job running beetwen 9am and 5pm with a MAXWAIT to 5.
After to be raised, the job stay in the plan the day after, and during the window time, it is able to run again.
That problem appeared after an update from oldest version than 6.x.xx to the new version of Control-M Server.
In fact there is a big issue in previous version before 6.x.xx.
MAXWAIT parameter wasn't use with Cyclic Job.
That issue has been corrected by BMC since version 6.x.xx.
To solve that problem, or to be as we has been before that update, you must add following line in the config.dat file on each Control-M Server.
CYCLIC_MAXWAIT=NOT_KEEP
It could ne necessary to stop and stat Control-M server to run correctly.
