Hi,
Putting a job ON ICE prevents the job being triggered without affecting the workflow.
Here are two ways you can stop this job from being triggered after the 20:30 run.
1) After the 20:30 job run completes(before 21:30), issue a sendevent command to put the job ON ICE, and later take the job OFF ICE after 22:30 hrs. This would skip both the 21:30 and 22:30 runs of the job. The following runs would be scheduled as usual.
Example: Putting the job ON-ICE and taking it OFF-ICE
This command puts the job ON ICE:
sendevent -J CNFB001B -E JOB_ON_ICE
This command takes the job OFF ICE:
sendevent -J CNFB001B -E JOB_OFF_ICE
Note: The above changes would be immediate.
2) If you know, by what time the 20:30 run would complete, you can set the job to avoid running during that specific interval.
Example: Prevent a Job from running during a specific interval
This example prevents the job CNFB001B from running between the hours of 21:15 and 22:40. For instance, if you know that the 20:30 run would complete by 21:00, you can set it to be put on ice by 21:15.
This command puts the job ON ICE at 21:15:
sendevent -J CNFB001B -E JOB_ON_ICE -T "DD/MM/YYYY 21:15"
This command takes the job OFF ICE at 22:40 p.m.:
sendevent -J CNFB001B -E JOB_OFF_ICE -T "DD/MM/YYYY 22:40"
Note: Kindly ensure the date format and time is in sync with your scheduler timings.
We recommend you to test this behaviour on a test job in your system to ensure the time and date format compatibility.
Additional Information:
Reference Guide
Hope this helps!
Regards,
Avinash