Is there a max run set?

How many days is the Keep Active field set for? (Found on scheduling tab at the bottom)

Hi Apoorv,

Is it the case that at the time of NDP the old instance of the job was in executing state? If yes, then you will see the 2 instances of the same job in monitoring domain but the previous day instance will will the cyclic flag off and will only complete its current execution.

If above is not true then as Bhanu Prakash Badiginchala mentioned, you should look at the Keep Active field.

If you don't want to run the 2 instances of the same job in any of the above case, you can configure the quantitative resource on the job.

Regards,

Ilyas Shaikh

HI Apoorv Chaturvedi

As mentioned by Ilyas Shaikh,  if the job(cyclic or not) is executing as of New Time, this job will be kept on Active as part of NDP selection mechanism also a new job is ordered to Active as part of NDP. that is why you may notice 2 Job instances.

But, The Control-M CYCLIC_MAXWAIT system parameter governs the Control-M Application behavior related to CYCLIC Jobs and MAXWAIT/Keep Active For nDays.

So, the CTM Application default behavior for CYCLIC jobs is to KEEP Cyclic jobs that had run at least once on Active regardless of it ended status until "MAXWAIT/Keep Active For nDays" is not exceeded. This makes sense to what is happening as mentioned by Bhanu Prakash Badiginchala if your current cyclic job does have "MAXWAIT/Keep Active For nDays" >  0, then CTM will keep them Active while not expired.

My Best

A>Gomes