Scheduling a job

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
mab_arif16
Charter Member
Charter Member
Posts: 87
Joined: Sat Mar 18, 2006 11:45 pm

Scheduling a job

Post by mab_arif16 »

Hi
A sequence needs to be fired every hour by cron tab ,but some times it takes more than one hour for sequence to run ,so when the cron tries to fire it again while its still running I get a warning DS.SCHEDULE;Job Must be reset before run
Does somebody have any idea how to get around this problem.The sequence has to be fired every hour

Thanks
Arif
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

What do wou want to do if it's still running?

If you want to abandon execution for that hour, simply detect its current status and, if it is DSJS.RUNNING, simply don't issue the run request.

If you want it to run every hour irrespective of whether it's currently running, then your solution must involve multi-instance jobs. You can use the time, or a timestamp, as the invocation ID.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: Scheduling a job

Post by chulett »

mab_arif16 wrote:A sequence needs to be fired every hour by cron tab
Every hour, or very hour by cron? Cron in and of itself is not sophisticated enough to handle that situation. You'll either need to handle it as Ray notes, or use an Enterprise scheduler (like Control-M) rather than cron if you have one.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply