100 job in one Sequence Job

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
vitumati
Participant
Posts: 27
Joined: Tue Sep 07, 2010 11:38 pm

100 job in one Sequence Job

Post by vitumati »

Helo Friends,


In my project I've requirement like...

I develop 100 jobs all independent each other(no dependency) But I need to design one sequence to trigger all jobs at a time.

Thanks.....!!
VijayKumar T
Abhinav
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Curious what you think is going to happen to your poor Windows server when you attempt to start 100 jobs (parallel or otherwise) at anything approximating the same time?
-craig

"You can never have too many knives" -- Logan Nine Fingers
vitumati
Participant
Posts: 27
Joined: Tue Sep 07, 2010 11:38 pm

Post by vitumati »

chulett wrote:Curious what you think is going to happen to your poor Windows server when you attempt to start 100 jobs (parallel or otherwise) at anything approximating the same time?


My QUESTION IS HOW I DESIGN 100 JOB IN ONE SEQUENCE ?


I'M NEW TO SEQUENCES?
Abhinav
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

First off, don't shout (all capitals is "shouting" and bad netiquette).

You can program 100 jobs by adding 100 Job activities to the sequence.

You will then grind your server into dust trying to execute them. You have been warned.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
MT
Premium Member
Premium Member
Posts: 198
Joined: Fri Mar 09, 2007 3:51 am

Re: 100 job in one Sequence Job

Post by MT »

Hi Vitumati,

depending on what you mean with
vitumati wrote:
... But I need to design one sequence to trigger all jobs at a time.
you could design a single sequence where you add a sequence to your jobs - even they are independend - in order to decrease the parallelism which will kill your machine (see the other comments).
So if you design for example 4 starting jobs and link 24 other activities to each of the starting job you will have aparallelism of four.
If your server is able to handle this you could try 6 parallel streams.

If your requirement means to start 100 jobs simultanously then I can only wish you luck and a short way to your servers reboot button :-)

regards
Michael
Post Reply