Would you like to learn to schedule a job on the last day of each month without using a calendar?


How about learning how Control-M can automatically adjust when a job runs if it happens to fall on a holiday or weekend by using the Confirmation Calendar feature?


If you'd like to learn how to make your job easier when scheduling in Control-M, both with and without calendars, we invite you to watch this Connect with Control-M recorded webinar on last Wednesday, August 31st. We demonstrated how to:



Schedule jobs to run or not run on specific days without using a calendar


Take advantage of Confirmation Calendars


•      Adjust rerun settings to affect the timing of cyclic jobs


This is the link on YouTube to the recorded session:



Connect with Control-M: Job Scheduling Techniques



Here is the Q&A for this webinar (Connect with Control-M: Job Scheduling Techniques)



Q: If the Maximum Reruns for a cyclic job is set to 0 that means it will run forever?

A. The newday process performs a stopcyclic if the Keep Active For (MAXWAIT) value is exceeded.



Q: Is there a limit for the Post Processing actions you can set for a job?

A: There is a limit set in version 8 for Do post-processing actions set to 99.



Q: Is it possible to set a cycle interval to minutes and seconds?

A: You can use days, hours and mins.



Q: What is the max number of specific times we can put?

A: Article 000120159

   You can put all the specific times that you need as long as they are not repeated.



Q: Can I change the cyclic intervals in the monitoring domain?

Q: When I change the interval of a job in the AJF, when will this take effect?

A: Yes, this will take effect after the next run time.



Q: If "No Tolerance" is defined, will the next execution get skipped?

A: Yes, the default for the Tolerance Parameter is 0.

   If the previous execution doesn't finish when the next specific time is reached, then the Cyclic Job will skip this execution.



Q: How do I enable the forecast option that you mentioned?

A: The Control-M/Forecast product would need to be installed and activated. If you do not see Control-M/Forecast available in EPD, please contact your sales representative.



Q: Can I schedule every other week without using Calendar?

A: You will need a calendar to do this because alternating weeks don't carry beyond the current month, just like alternating weekdays don't carry beyond the current week.



Q: Can we use a normal calendar with specific dates?

A: All the Regular calendars are based on specific dates.

   As well, in the Job definition you can use the "Specific Dates" option, and with this, you don't have to create a calendar.



Q: Can you explain RBC's importance?

A: With Rule-Based Calendars you can create complex scheduling definitions,

   You can have the Rule-Based Calendar definition with the "Advanced Scheduling" option, and with these calendars, you don't have to worry about maintaining the calendar definition every year.

   Article 000029568 contains additional information that may be helpful.



Q: Regarding Confirmation Calendars, how is the And/Or option used?

A: The And/Or option only applies to the Month Days and Week Days selections when using the Advanced Scheduling option.

   Confirmation Calendars act with an "AND" relationship to the rest of the schedule.



Q: What happens when you set a job's rerun interval to Start?

A: All intervals between executions are based on the start time of the job's previous execution.



Q: We have an hourly cyclic job, and we want to rerun it after a 5-minute wait upon an abend. We have it set up for "rerun" upon failure, but must manually use the "run now" option to get it to execute. Can our scenario work without manual intervention?

A: If you include a "Stop Cyclic" action, you can have the job perform an automatic rerun on failure. Be aware that the job will no longer be cyclic.

   Because cyclic jobs are already set to rerun regularly, to do this modification of the rerun schedule without ending doing "stop cyclic" would require manual intervention.



Q: In a 24 hours batch window, is there a way to skip an iteration of a cyclic job in the middle of its time range?

A: You can accomplish this by specifying specific execution times.



Q: If you use an interval of days do you need to use the Keep Active For (MAXWAIT) Days?

A: Yes.



Q: If the tolerance is missed, does that mean that job event will not be run at all?

A: Yes, that execution time will be skipped. When the next specific time arrives, the cyclic job will resume normal processing if the job is not in execution.



Q: Cyclic job: set up job for 4 specific times, 9:00, 9:10, 10:00, 11:00. Tolerance set to 5 mins. If the 9:00 execution is still running at 9:10 and completes at 9:25, will the job still run at 9:10?

A: The 9:10 execution will be skipped. Once the 9:00 execution ends at 9:25, the job will not execute again until 10:00.



Q: Is there a recommended cyclic minimum for best performance? Would a cyclic job with rerun interval of 0 min impact the performance of Control-M?

A: It depends on the performance of the machines where the Agent and Control-M/Server are installed. Each additional submission and execution increases the overhead on these machines.



Q: What is the "Tolerance Minutes" parameter?

A: This is the maximum delay in minutes permitted for a late submission when selecting a specific time (e.g. 5 minutes).



Q: How can we set up a cyclic job to execute past newday?

A: If CYCLIC_MAXWAIT (Control-M/Server system parameter) is set to KEEP (default), cyclic jobs are only deleted from the Active Jobs database after the expiration of the Keep Active for parameter.

   More detailed information on these parameters is included in the Control-M Administrator Guide.



Q: If you have a job scheduled let's say on Monday - Friday except for holidays and to roll back, so let's say 4th of July is Tuesday, will I have 2 of the same jobs running on Monday? and if so how can that be stopped so that 2 of the same jobs don't run on the roll back day?

A: If you are using a Confirmation Calendar to shift to the previous working day, you will have only one instance on Monday.



Q: What does the "shift by" parameter do in RBCs?

A: The "Shift by" option sets the number of working days the job can be moved when the RBC does not match the Confirmation Calendar.



Q: How are RBC different from Periodic calendar?

A: Periodic calendars: Enables you to create a pre-defined calendar based on different calendar periods that you define. Periods can be nonconsecutive, of varying length, and overlapping.

   Rule-based Calendars: Enables you to create a pre-defined calendar that is based on specific rules.

   You can use the options for Job scheduling like Month days, week days, Advanced scheduling, etc.



Q: Will Forecast show previous days?

A: Yes, it will.



Q: In the demonstration, you were scheduling jobs at intervals like 5 or 10 minutes, it appeared in the description field, but where exactly did you set that up?

A: In the Planning Domain, in Job Properties --> Scheduling --> Rerun Settings --> Set



Q: If we use tolerance, its effect will be on the next iteration. How does this affect the subsequent execution times of the cyclic job?

A: If the current time exceeds the next time plus tolerance, then that iteration of the job will be skipped. Scheduling times can be affected if the interval is based on job start or end times.



Q: Please describe "On-Do" conditions that apply to reruns.

A: From the demo, you have the option to use number of failures (FAILCOUNT), number of executions (RUNCOUNT), or reruns (RERUNNO) in the on/do statements.



Q: If cyclic job fails, and it takes a while to fix, will the cyclic start from the time we fix, or will it keep running while the one is failed?

A: By default, a cyclic job will continue its schedule regardless of an individual execution ending NOT OK. You can prevent this for an individual job by using an On-Do action to "stop cyclic". You can change this behavior at the Control-M/Server level by changing the Control-M/Server system parameter CYCLIC_RERUN from "OK" to "NOTOK".

   More detailed information on these parameters is included in the Control-M Administrator Guide.



Q: Is there any way to prevent a "standard non-cyclic" job from being rerun? When you click Rerun the job will just not be submitted...

A: You can set this in security settings at the user or group level, not through the job definition.



Q: Can a rule based calendar be used everywhere that a regular calendar can in scheduling definitions?

A: Only regular calendars can be used as confirmation calendars.



Q: If we use Forecast for previous, how can we use Archive and history options?

A: Forecast shows, based on current schedule, when things would run. The history domain shows archived viewpoints that have real data about previous days.



Q: I have a job that starts at 23:00 hrs and my NDP is at 00:00. And the job is setup to run between 23:00 and End of Day. The server is unavailable and it became available after 00:00 hrs. So now will the job run immediately or it will wait for 23:00 hrs?

A: If the Server becomes available before the 00:01 hours it will run. If not and Keep Active For (MAXWAIT) is set accordingly, the job will run again at 23:00.



Q: Can you run a job based on relative days, like 5th business day of the month?

A: Yes, you need to have a calendar for business days and select the option "based on calendar" using this calendar. Then, select the option "Relative Calendar Days from Start/End of Month/Period" and select the 5th day.



Q: If a job fails, I want that job to wait for 10 min and then rerun automatically. Is that possible through Rerun Setting in Actions tab?

A: The interval under Rerun Settings can be set to rerun every 10 minutes from a job's end, even for non-cyclic jobs, and a "Do rerun" action will honor these settings.



Q: If a cyclic job runs every 5 mins is there a way to get late sub alerted if it did not run within 5 mins of the previous run?

A: The late sub alerts will work only for the first execution.

   We have the two following enhancement requests open: