DSXchange

It can be run in the command window of Administrator, which you will already have connected to a specific project.

You must have exclusive access to the project.

Could this be another 8.0 bug? It works ok in 7.5.1.

Welcome aboard. Each operator in each job takes only what it needs. You do not allocate any space; the requests are built in to the operators. Nothing in DataStage takes "the full allocation regardless of need". Therefore you already have optimal allocation. Your issue is one of total load...

samplify wrote:Thanks in advance! (and hope its not a UNIX solution!)

I'd be inclined to write a before-job subroutine (or just a routine to be invoked from a Routine activity in a sequence).

In a TRANSFORMER stage downstream on the reject link.

If you choose Overwrite as the Data Set write method it is deleted and re-created. You can verify this by inspecting the score.

No, because I don't currently have access to Enterprise Edition.

YOU try it, and let us know. I can only guess.

Because that's how whoever write the Execute Command activity wrote it.

You may as well ask why we need to have the SELECT clause first in SQL, even though the FROM clause is parsed first.
Why can't we write

Why that particular number?

If 10,000 is good, why not 10 million? Should be 10,000 time better, shouldn't it?

Do you understand precisely what this Array Size parameter does?

We don't do "urgent". DSXchange is an all-volunteer site whose members post as and when they can, usually only if they have something constructive to contribute. If you want "urgent" support (and I question that you acually "need" it in this case) sign up with your sup...

Add a reject link to handle the row rejected by the database, and set the row limit on this link to 1.

If you can arrange to have your source data sorted by the five grouping columns, and advise the Aggregator that this is the case, your execution time for that stage will reduce by orders of magnitude.

Try it and find out, and let us know. My guesses (since I'm not in a position to try) would be indeterminate for the Compare() functions because I don't know what the value of EXSTCRR_TRANS.MW is. Once you've done a Trim() you have a string, so you don't actually need the Compare() function - you're...

You can't have that without business rules. Do you mean inclusive or exclusive counting? Ultimately these will mean one or two extra adjustments of plus or minus one in the formula, but you must get them nailed down lest we waste time giving you wrong advice.

What's the answer?

The solution will depend on your business rules for handling situations where the day number is not the same in the two dates.