DSXchange

NPROC is a UNIX setting. Your UNIX system administrator will be able to help. You *may* be able to get away with increasing ulimit -n but the better long-term solution is to increase NPROC as well. Note that some UNIX implementations use a slightly different name for this parameter - it's the number...

One of your record schemas includes at least one subrecord. Find it and make sure it's being properly dealt with.

Use a routine in the master control sequence that (a) checks how many instances are already running and (b) invokes the sub-sequence via DataStage API functions.

vivekgadwal wrote:OP - Please keep in mind any of these approaches will have an affect on the performance.

No they won't. They'll have an effect. "Affect" is a verb.

Lots of them. Libraries, for example: VMxxxxxx.so (or VMxxxxxx.DLL).
The same is true for Ascential, for example the name of the mainframe runtime library.

Yes I was able to review this problem. Craig's point about parallel execution is a red herring; the requirement is to distinguish between zero rows processed and non-zero rows processes, irrespective of the number of nodes. Therefore the routine is fundamentally correct, provided it is passed the na...

You can write your own stages and replicate what a Transformer stage does, but why would you reinvent the wheel?

Yep, some of us date back to version 1.0 (and further!) - some of the knowledge is still there in the ol' grey cells! Now to your question. Some advances do get backdated into earlier releases - for example version 7.5.3 contains some goodies first released in version 8. So don't be backwards about ...

Otherwise the problem reduces to a brain-dead answer to the exact question. The two constraint expressions would be of the form:

Nothing any more. Ascential Software acquired the vendor of the parallel execution engine, a company then called Torrent Systems. Previously, that company had been called Applied Parallel Technologies.

Actually that's easy, and is exactly what the job control code generated by compiling a job sequence does. In summary, it makes use of the fact that the DSWaitForJob routine can wait for an array (a dynamic array) of job handles. It returns any time any of the jobs finishes, the code can return to a...

That's the big question, though, isn't it? Just how are rows allocated to the different outputs? harikmar remains strangely silent on this question.

Your reply to Arnd's question was not what I'd call logic. We (you) need to know what are the rules for duplicating one (or more?) particular row but not others. Perhaps you could ask your interlocutor?

harikumar wrote:NOTE:without using switch AND filter stages

This smells like an interview question to me.

I believe strongly that interview answers should accurately reflect the interviewee's own knowledge and skills.

1. Probably.
2. No idea. What do you mean by "simplified"? The DataDirect drivers that ship with DataStage have their own documentation.