DSXchange

Try the same trick again, but this time re-selecting VERSION after the invalid project.

What do you believe the purpose of each of these stage types is? Research the Advanced Parallel Job Developer's Guidenor on-line help. Then post a more specific question. And don't seek help via private message or email unless you're prepared to pay for that help .

It's an old trick but a good one.
Try to invoke Version Control but give an invalid project name as the version project. That forces it into the "select project" dialog.

No problem. Probably easiest is to create another job - a server job is recommended, since only one row needs to be processed. Use a job parameter for the job status, assigned its value from the $JobStatus activity variable of the upstream job. Use another job parameter for the name of the job upon ...

Select the Stage Types branch of your Repository. Using the New tool/menu, create a new parallel stage type. Do your coding in the GUI exposed after you choose your stage type (build, custom or wrapped).

If you want to use MetaStage to perform lineage analysis or "where used" analysis for the table, then promoting the table definitions is mandatory.

There are no duplicates in a Transformer stage.

Welcome aboard.

Your issue is neither similar nor related to the one on this thread. Therefore you need to post a new thread with your question.
But, first, Search the forum - you will find that this message has been seen before, and questioned and answered here.

Obviously one million rows is still below the "large" threshold.

Are you using write cache for the target hashed file? If so, rows/sec screams along while rows are being written to memory, then appear to reduce. Actually at this time all rows have been processed into memory and are being flushed to disk; because the clock keeps running the rows/sec figure appears...

There are no data types in text files - only text. Therefore there can be no null - just a text representation of NULL. You can advise the SequentialFile stage what this representation is on the Format tab for the default for the file, or in the column properties (Columns tab) for per-column specifi...

The Routine activity treats a return value of 0 as "OK" and any non-zero value as a failure. Change this behaviour by creating a trigger that allows any positive value.

The double-quote technique is part of the SQL standards. They are referred to as "quoted identifiers". The technique works in all databases that are compliant with SQL standards.

Welcome aboard. I don't use it, but it's being demonstrated at IOD2007. I can't give you any information about how widely it's been adopted. But surely someone in IBM would know - maybe your account rep hasn't asked the right people?

Dump the data to a text file, and there examine it with a hex editor such as UltraEdit.