there is nothing wrong in calling all the job in a single sequence
![Wink :wink:](./images/smilies/icon_wink.gif)
Moderators: chulett, rschirm, roy
Wrong. There is actually no limit.manishsk wrote:I have worked on modules which involved around 150 - 200 jobs running one shot. At such place I can't go for sequencers.
Yes ray. You are correct, that we can create hierarchy and some ways to simplify the things. But when huge number of jobs comes I feel its better to cocentrate on jobs rather than putting more development time in developing job sequences. By BASIC code its easy to track down things, its what I feel.ray.wurlod wrote:Wrong. There is actually no limit.manishsk wrote:I have worked on modules which involved around 150 - 200 jobs running one shot. At such place I can't go for sequencers.
To keep things easy to read/understand, build a hierarchy of control, using Job Activities to call other job sequences.
I'm confident you can find some criteria on which to base the grouping of your jobs.
So - and I've taken it as a given that your hardware is up to 150-200 simultaneous jobs - there is no reason to avoid job sequences just on the basis of number.
Did you know that, if you right click on a Job Activity in a job sequence design, you can "drill down" to the next level down (that is, to the job or job sequence that's invoked)? Just choose Open Job from the pop-up menu.
Oh, and it's job sequences, not sequencers. Or were you really referring to Sequencers? If there's a limit on the number of links, you can create a hierarchy of Sequencers for decision making in a job sequence.
Sorry, I didn't explain what I'm thinking about.chulett wrote:Actually, there is! It's called another Sequence job.Thibal wrote:About my "cleanliness" issues, I'll find tips when developing (It's a pity it doesn't exist a kind of Sequence Container)
gbusson wrote:Thibal wrote:Sorry, I didn't explain what I'm thinking about.chulett wrote: Actually, there is! It's called another Sequence job.
Indeed Sequence Job could call another Job Sequence made up of a job activity and two routine activities but it can't transmit in parameter the name of the job to launch.
If I'm wrong, I wouldn't say anything more before the end my development
A solution could be using Job Sequence to call a Routine Activity with my current "Job Control" Code
This is exactly what i was saying. Job Sequence is good indeed, but not as flexible as Job Control.
Instead of Job Activity, i use a Routine Activity to run jobs.
If you prefer, if Mr Wurlod uses Job Sequences, it can be good (even if Job Control can be better in some cases , no one is perfectkumar_s wrote:Thibal wrote: If Mr Wurlod uses Job Sequences, it can't be bad![]()
quote]
BTW, nothing like 'BAD' in DataStage, where IBM/Ascential might have purposefully introduced in their own produce. Its all about how effeciently we use the available option to acheive the task in an easiest way.
Obviously, Pros and Cons are available in both method. Job Sequence were not versatile in earliar versions. Now many built in features as been introduced, just drag-drop kind.
Still there are many situations where Job control wins the Job Sequence, as Craig mentioned. Nonlinear Itrerations, Custom error logs, Partial restratablility.....
Again its all depends on the effeciency of coding/coder.
Its all depends on the person and his profeciency in his approach.
Mr. Wurlod please use Job Control from Next Time !!Thibal wrote:kumar_s wrote:If you prefer, if Mr Wurlod uses Job Sequences, it can be good (even if Job Control can be better in some cases , no one is perfectThibal wrote: If Mr Wurlod uses Job Sequences, it can't be bad![]()
quote]
BTW, nothing like 'BAD' in DataStage, where IBM/Ascential might have purposefully introduced in their own produce. Its all about how effeciently we use the available option to acheive the task in an easiest way.
Obviously, Pros and Cons are available in both method. Job Sequence were not versatile in earliar versions. Now many built in features as been introduced, just drag-drop kind.
Still there are many situations where Job control wins the Job Sequence, as Craig mentioned. Nonlinear Itrerations, Custom error logs, Partial restratablility.....
Again its all depends on the effeciency of coding/coder.
Its all depends on the person and his profeciency in his approach.)