How to schedule a job for centain intervals that is dependant on other hourly jobs?

[ziaul_hoque1]

Hi support community,

I hope you would be able to help me out which will be greatly appreciated.

I have a job that I only needs to run on certain times but this job is dependant upon other jobs that run every two hours.

So, I have this sequence:

Job A: runs at certain times and it is dependant on Job B

Job B: runs every two hours which is also dependant on Job A

Job A: which runs every two hours from 11an until 11pm everyday.

How can I accomplish job A to run at certain hours?  You see, Job B has to complete which copies an application and I would like to take that application and rername that application to preserve data.  Please let me know if you need more infromation.

Thanks,

[Derrick Au]

Hi,

Firstly, the sequence should be re-defined. The recipe you have right now leads to a circular reference where Job A is dependent on Job B and Job B is dependent on Job A--this is not allowed.

[ziaul_hoque1]

Hi Derrick,

Thanks for your respose.  Actually Job B is not dependant on Job A.

Job A has to complete normally for Job B to start.

Job C (problem child), which would be dependant on Job B needs to start on certain times after Job B completes normally.  Let me know if I am making sense.

Thanks,

[Derrick Au]

Hi,

In Job C, try adding a job dependency on Job B completing normally, and setting occurrence selection to last occurrence.

[ziaul_hoque1]

Hi Derrick,

Job B repaeats every 2 hours, up to 7 times.

So, I need to create  new jobs for Job C for the times I would like to have it run and then specify a time window; and then make it dependant on Job B for the last occurance?

Thanks,

[Derrick Au]

Hi,

Yes, that sounds right. So even when Job B (7) completes normally, and Job C continues to run (outside of Job B's time window) -- Job C only checks the last time when Job B ran with successful completion.

If this is not the case, please let us know exactly what your scheduling requirements are: start and end times for each job involved, and dependencies between them. OP wasn't very clear.

[ziaul_hoque1]

Hi Derrick,

Yes, this this is the case.  Job C should only run after Job B completes successfully on the second repeat [Job B (2)].  I set it up per your suggestion to give it a test run.  However, I notice strange behavior on the Job Activity panel; where it’s showing up twice with different run times.  Please see the attached.

Thanks,

[Derrick Au]

Hi Ziaul,

Let's remove any un-run instances of Job C from the schedule entirely. From Job Definitions, disable the job ... and then click on the history tab to ensure that the job has been removed. When you re-enable Job C and select today as the effective date, then Job C should be added in today's schedule correctly plus however many future days to include in the schedule.

[ziaul_hoque1]

Thanks Derrick,

I have followed your suggestion and I see it waiting on dependency on the last run of Job B run (7).  I will wait and see if Job C would kick off right after the second run for Job B completes, which is estimated to end at 1:51pm.

I also have 'All must be met" radio button tic marked on the Dependency tab.  Should this be the case?

[Derrick Au]

Hi Ziaul,

Hmmm sounds like the disabling did not remove any un-run instances of Job C completely from the schedule. Try disabling Job C, check on the history tab, and if Job C is disabled correctly then future dates scheduled should be removed. Once all future dates have been removed, then it would be okay to re-enable Job C with today's date as the effective date. Job C should not be waiting on dependency on the last run of Job B run (7) -- since Job C does not repeat, and is scheduled between 1:30pm-2:00pm. So try again once more but give Tidal a little more time to process in between disabling and re-enabling Job C.

And All must be met is fine.

[ziaul_hoque1]

Hi Derrick,

I disabled and didn't notice any future schedule jobs showing on the history tab.  I then logged out of Tidal and set it one more time but It's still showing the same.  Do you think there should be an offset value on the dependency tab?

Thanks,

[Derrick Au]

Which version of Tidal 6 are you running?

[ziaul_hoque1]

Version 6.1.0466

[Derrick Au]

Aha! Please check out https://tools.cisco.com/bugsearch/bug/CSCuf39173

[ziaul_hoque1]

I have actually disabled the job by right clicking and selecting 'Disable' menu and I didn't see any future job schedules on the history tab.  I usually do not uncheck "Enabled" from the edit mode.

Thanks,