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,

[ziaul_hoque1]

Hi Derrick,

...looks like the job timed out.  Any idea why that would happen?

Thanks,

[Derrick Au]

Please upload a screenshot(s) of audit log, and dependency tab from job activity screen for both Job B and Job C

[ziaul_hoque1]

Please find the attached.

Thanks,

[Derrick Au]

Hi Ziaul,

It's kind of tricky when making these intraday changes. The dependencies are not correct according to the screenshots. Job C has a time window between 1:30pm-2:00pm, but yet it is looking when Job B run (7) completes which will not occur until much later. As a workaround just manually override the timedout job to run.

But now let's take a look at the schedule on 5/14/2015. Double click on Job C scheduled to run between 1:30pm-2:00pm, and click on dependency tab. Do you see anything different? Job C should be pointing to a different instance of Job B? If that is the case, then starting tomorrow the job should flow correctly.

[ziaul_hoque1]

Hi Derrick,

I manually ran the timed out job by overriding.

Actually, I am afaraid I do not see any difference for tomorrow's job except that run #7 for Job B is currently scheduled.  Please see the attached (Forum 3).

Thanks,

[Derrick Au]

Hi Ziaul,

Not what I was expecting. But is there any possibility of setting Job B from running new occurrence to same occurrence? Job C that is scheduled to run from 1:30pm to 2:00pm will then look at the last completion time of Job B. Last occurrence is definitely the last run for that series, and to try and use an offset may throw things out of synch.

[ziaul_hoque1]

Hi Derrick,

Yeah, I have found this to be kluge and struglling with it for a while now.

Sure, I can change the job execution for Job B to the same occurance.  Would it cuase any other issues or get out of sync from its predecessor?

Thanks,

[Derrick Au]

Hi Ziaul,

Is predecessor Job A running a new occurrence each time as well? If all jobs involved gets converted over to running just the same occurrence, then there would be no issues (with each successor job dependent on one above and selecting last occurrence as an option).

Cheers,

Derrick Au

[ziaul_hoque1]

Hi Derrick,

Thanks for you continued support.   I am not sure what the outcome will be as there is a daisy chain of dependency for Job C in the stream.  Please see the attached (forum 4).

Thanks,

[Derrick Au]

Hi Ziaul,

I see what you mean, this goes beyond Job A B and C since there are predecessors. As long as they behave similarly running the same occurrence then they should be fine. As you noticed when running a new occurrence for a predecessor job ALONG with successor job dependent on predecessor using last occurrence.

BR,

Derrick Au

[ziaul_hoque1]

Thanks Derrick,

I appreciate your inclination to help me out on this.

When I mark Job A (050_GLPKG_RT_CUBE) to rerun same occurance, It gets hooked onto Run #1 for all instances.

Do you have any other suggestions?

Regards,

Zia

[Derrick Au]

What is meaning that it gets hooked onto Run #1 for all instances?

[ziaul_hoque1]

Sorry for not clarifying!

What I meant is that all the instanaces for Job Activity are tagged as:

050_GLPKG_RT_CUBE (1)

050_GLPKG_RT_CUBE (1)

...........................................

...........................................

050_GLPKG_RT_CUBE (1)

and all of its predecessors show up for run #1.

Thanks,

[Derrick Au]

That doesn't sound right -- there should only be a single instance of 050_GLPKG_RT_CUBE(1). Would it be possible for you to email me a screenshot of what is on your job activity pertaining to these set of jobs and related predecessors?

Thanks,

Derrick Au

Backoffice Production Support

Millennium Management LLC

666 5^th Avenue, New York, NY 10103

Tel: (212) 708-4671

Mobile: (646) 630-1675
email: derrick.au@mlp.com

millennium

[ziaul_hoque1]

Hi Derrick,

I reverted back and the schedule is giving me a different problem where today's schedule got disarrayed and I can't seem to replicate the issues I saw beofre where 7 instances of run #1 were showing up.

Please see the attached.  This is the setting I currently have, which won't work becuse its predecessors are not scheduled.

Thanks,

Zia