DSXchange

Rekha - you don't need to completely repeat your first post. When I declare the stage with no inputs or outputs I do get that option, but that stage is only used to create the key, not to use it (if I understand the docs correctly). Did you specify a block size of 1? Do you use a surrogate key stage...

Many people here would surely enjoy assisting. But you need to be a lot more specific on what type of help you need and what you have tried so far.

What kinds of loops are S1 and S2 (lists? counted?) and when the job stops can you try a reset to see if you get information in the log entry "from previous run"?

Reset your job and see if you get more informatin. The only reason that DataStage give the sed/dbx message is because something has aborted and DS tries to see the stack.

The "pivot" stage will do this for you.

Welcome to DSXchange, abhirms. When I checked the Search function for the text "Fatal Error: waitForWriteSignal(): Premature EOF " I got 25 threads.

But in order to be certain what the cause is you will need to supply some more error information.

I have tried to see where the Block size can be set with the V8 Surrogate key generator and cannot find it! What block size did you specify?

The jobs are not aborting because of that message, it is an informational message shown after an error occurs.

The transaction with wave processing will only work if there is another MQ writer that closes the transaction.

Hmmm "1234567890123" is displayed as "12345678901.23". How many characters is that?

You can use scp in a server job. But as there is no stage to do this, you will need to shell out.

Your sort stage lets you choose how to handle partitioning - by default it will not repartition so you don't need to repartition after the sort.

I now see what you mean. I'm surprised at that behaviour but am not at a site where I can check to see if it works the same way in my implementation. I would expect constraint violations to be caught in the reject link instead of causing a job abort.

The post is marked as "resolved" -> is that the case?

jd - now I'm not sure if what I posted made sense...