Sequencer Issue

prasanna2100 · Post by **prasanna2100** » Mon Jun 12, 2006 11:47 pm

hi all,
iam getting this controller problem ,while trying to run a sequencer.

what can be the problem ??

kris007 · Post by **kris007** » Tue Jun 13, 2006 12:00 am

prasanna2100 wrote:hi all,
iam getting this controller problem ,while trying to run a sequencer.

what can be the problem ??

Are you sure you are using DS390? as you cannot create sequence jobs in MVS enviroment.If you are using either serv/parallel edition let us know the specific error you are getting.

prasanna2100 · Post by **prasanna2100** » Tue Jun 13, 2006 12:18 am

iam sorry krish,its the server edition

ray.wurlod · Post by **ray.wurlod** » Tue Jun 13, 2006 1:07 am

So what's the problem?

A Sequencer can only make an "any or all" decision on its inputs. There's naught that can go wrong with it.

I suspect you mean "job sequence".

prasanna2100 · Post by **prasanna2100** » Tue Jun 13, 2006 2:43 am

i have developed q squencer with 12 independent jobs.
while executing the sequencer iam getting this error

SEQ_J_TFM_F41003..JobControl (@J_TFM_F41003): Controller problem: Error calling DSRunJob(J_TFM_F41003_Trim), code=-14
>>
>>[Timed out while waiting for an event]
>>
>>SEQ_J_TFM_F41003..JobControl (fatal error from @Coordinator): Sequence job will abort due to previous unrecoverable errors
>>
>>then the sequnce aborts
>>
>>when I run individually the sequence it executes. Please suggest.

chulett · Post by **chulett** » Tue Jun 13, 2006 6:56 am

That's too many at once - run less than 12 simultaneuously.

kumar_s · Post by **kumar_s** » Tue Jun 13, 2006 9:29 am

As mentioned that may be due the server over load by triggereing 12 jobs at a time by a JobSequence.
You can try to give pause between job which are called.
Search the forum from more information.

ray.wurlod · Post by **ray.wurlod** » Tue Jun 13, 2006 3:29 pm

How many CPUs are in your DataStage server machine?

If this is a small number, and you are asking it to do so many things at once, is it any wonder it reports being overloaded?

Can you juggle two balls? Three? Twelve?!!

A design such as that below guarantees that at most two jobs at a time will be running.

Code: Select all

Job Activity ---> Job Activity ---> JobActivity ---> Job Activity
Job Activity ---> Job Activity ---> JobActivity ---> Job Activity

prasanna2100 · Post by **prasanna2100** » Tue Jun 13, 2006 10:17 pm

thanks for the information guys,
do you guys have any information on &PH& directory...

ray.wurlod · Post by **ray.wurlod** » Tue Jun 13, 2006 10:44 pm

Yes.

You, too, can have it by the simple expedient of searching the forum.

It may be more efficient to use both phantom and &PH& and perform a search for all terms.

This probably should have been a new thread.

sb_akarmarkar · Post by **sb_akarmarkar** » Wed Jun 14, 2006 5:55 am

Is that sequence having option check as automatically handle activity that fail...if any activity fails it aborts sequence with that error....

Thanks,
Anupam

Krazykoolrohit · Post by **Krazykoolrohit** » Tue Jul 11, 2006 8:08 am

I am running only 3 jobs at a time and still getting this error.

Few questions:
In job resource i see there are many jobs running although not of my project. Does this effect concurrency?

NOTE: We were able to run 17 jobs simultaneously just 1 week ago

ray.wurlod · Post by **ray.wurlod** » Tue Jul 11, 2006 9:33 am

Not concurrency, just total load. Monitor your operating system to determine where the bottlenecks are; CPU, memory, I/O throughput, network bandwidth are the primary candidates.

Krazykoolrohit · Post by **Krazykoolrohit** » Tue Jul 11, 2006 9:36 am

If something was a bottleneck then how come we were able to run 17 jobs simultaneously at some point of time. anyways i will try and run all of them in night ensuring no other user is connected.

will update this post. thanx

ray.wurlod · Post by **ray.wurlod** » Tue Jul 11, 2006 9:37 am

17 lightweight things might load the system less than two heavy-duty things.

DSXchange

Sequencer Issue

Sequencer Issue

Re: Sequencer Issue