Scheduling a job for executing continuously

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
Amar_nath
Participant
Posts: 56
Joined: Tue Apr 18, 2006 5:03 am

Scheduling a job for executing continuously

Post by Amar_nath »

Hi,

We have source feed as XML Messages, so the data feed is continuous.
So our requirement is to have that extraction job continuously running for lets say 8 hours, in result it will extract and load data in Staging area continuously.

I am aware of two work around -
1. To schedule the job e.g. after each 30 mins from monday to friday
2. Using UNIX script repeats the job execution

I dont want to use this two options. Is there any built in function or scheduling facility that will allow me to run that job continuously?

Regards!
Amarnath
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Are you sure that your job will finish within the 30 mins? What if it over-runs?

In the sequencer, you can make the job sleep for "30 - x" seconds, where x is computed using the job start and finish time.

Alternatively you can make your input read a pipe making it realtime load.
keshav0307
Premium Member
Premium Member
Posts: 783
Joined: Mon Jan 16, 2006 10:17 pm
Location: Sydney, Australia

Post by keshav0307 »

Use any third party tool like Control-M
Amar_nath
Participant
Posts: 56
Joined: Tue Apr 18, 2006 5:03 am

Post by Amar_nath »

Hi keshav,
I dont have Control-M for scheduling. And I am avoiding use of UNIX scripting for keeping maintanance easier of my jobs.

Sainath,
I have tested that job gets finished in 10-13 mins everytime still I am keeping a buffer of 15-17 mins more.
I am looking in sequencer for this sleep time option.
Can you please provide me some more details on that.

Thanks,
Amarnath
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Why not create the job as a "WISD" or real time job, expose it as a service? Then it truly can "execute continuously" and process messages in real time. Depends on what exactly these "messages" are and how they are (or could be) delivered.
-craig

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