job sequence

attu · Post by **attu** » Thu Jun 14, 2007 10:25 am

I have 4 jobs and after each job completes i need to run a script , i need to know whether i can use before after sub routine in each job or in the job sequence i can use execute command stage.

Thanks all

chulett · Post by **chulett** » Thu Jun 14, 2007 10:31 am

attu · Post by **attu** » Thu Jun 14, 2007 10:35 am

Craig,
Thanks for your prompt reply

So I should use an after job sub routine at the job level. right?

is it a best practice ?

chulett · Post by **chulett** » Thu Jun 14, 2007 10:40 am

Either one can work, it's your call. Me, I'd prefer it be a discrete step in the Sequence job, each Job Activity stage would have a trailing Execute Command stage.

attu · Post by **attu** » Thu Jun 14, 2007 11:01 am

thnx Craig,

for every job activity stage i have routine activity stage attached and an execute command stage attached, but the next job in the sequence should only run when the script in the execute command stage finishes ...how would i accomplish this?

any suggestions

thanks

dspxguy · Post by **dspxguy** » Thu Jun 14, 2007 2:01 pm

OK conditional trigger in COMMAND EXEC ACTIVITY .

chulett · Post by **chulett** » Thu Jun 14, 2007 4:07 pm

Exactly. One of them between the EC stage and the next JA stage. And make sure your script passes back a non-zero exit status if something goes wrong in it, otherwise your next job will always think it ran ok and things will not stop.

attu · Post by **attu** » Fri Jun 15, 2007 9:25 am

Thanks for the help,

The script will load data into a table which will be used by the next job, in that case after the script finishes running and moves on to the next job and if the table is still being loaded. How will it affect the next job?
Any thoughts on this

Thanks

JoshGeorge · Post by **JoshGeorge** » Fri Jun 15, 2007 11:26 am

Preempt such a situation. Make sure your script does not return its control back to datastage without completing what it is meant to (ie. loading complete data into respective table). If you have linked stages in sequential order, sequence will move from one stage to next only in that order and also only after the current stage finishes.

attu wrote: The script will load data into a table which will be used by the next job, in that case after the script finishes running and moves on to the next job and if the table is still being loaded. How will it affect the next job?

chulett · Post by **chulett** » Fri Jun 15, 2007 1:46 pm

First thought... Why use a script to 'load data into a table', isn't that what you bought this fancy ETL tool for? Why not use a job?

attu · Post by **attu** » Fri Jun 15, 2007 2:03 pm

Craig I dont know why they are using script.

In the end of my final job activity after the job is processed and runs a script from the command execute stage and after that it goes to routine activity stage for job status.

How will I end the whole sequence after all jobs have ran successfully?
can i use end loop activity stage?

sun rays · Post by **sun rays** » Fri Jun 15, 2007 2:12 pm

If you are not going to do any iterations then do nothing. The sequence automaticaly stops after the last activity.

mystuff · Post by **mystuff** » Fri Jun 15, 2007 2:17 pm

Craig I dont know why they are using script

What's your database?

attu · Post by **attu** » Fri Jun 15, 2007 2:22 pm

sun rays wrote:If you are not going to do any iterations then do nothing. The sequence automaticaly stops after the last activity.

So after routine activity stage no out put link....

Mystuff it's Netezza

JoshGeorge · Post by **JoshGeorge** » Fri Jun 15, 2007 6:58 pm

You can put a Sequencer stage in the end with mode set to 'All' and fill in the 'Logging Text'.