How identify Schedule Object triggered in job with 2 associated schedules [message #663645] |
Mon, 12 June 2017 17:16 |
athensromania
Messages: 46 Registered: July 2007 Location: Valencia,Spain
|
Member |
|
|
Hi all,
I've been running some test, to run a job using two different schedule objects.
In example, job will be exexuted at 10 on Mondays using using schedule 1 and at 12:25 on Tuesdays using schedule 2.
Is it posible to know which schedule has triggered the job execution? I've looking data dictionary views and I can't find anything useful.
Thanks and Regards.
|
|
|
|
|
|
Re: How identify Schedule Object triggered in job with 2 associated schedules [message #663652 is a reply to message #663645] |
Tue, 13 June 2017 02:26 |
athensromania
Messages: 46 Registered: July 2007 Location: Valencia,Spain
|
Member |
|
|
Hi,
in example for this scenario:
- If it executed for schedule 1 --> Action 1, not execute action 2
- If it executed for schedule 2 --> Action 2, not execute action 1
Instead of using a configuration table to check if action 1 or action 2 have been executed at the same day.
Just re-thinking a dirty solution could a lookup table clonning repeat interval (Day,Time) with action to be executed in case if it match.
Thanks and Regards.
|
|
|
|
Re: How identify Schedule Object triggered in job with 2 associated schedules [message #663654 is a reply to message #663652] |
Tue, 13 June 2017 05:57 |
John Watson
Messages: 8960 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
athensromania wrote on Tue, 13 June 2017 08:26Hi,
in example for this scenario:
- If it executed for schedule 1 --> Action 1, not execute action 2
- If it executed for schedule 2 --> Action 2, not execute action 1
Instead of using a configuration table to check if action 1 or action 2 have been executed at the same day.
Just re-thinking a dirty solution could a lookup table clonning repeat interval (Day,Time) with action to be executed in case if it match.
Thanks and Regards.
I don't understand this. One schedule can be attached to many jobs, not the other way around.
|
|
|
|
|