DSXchange

Have you mounted the other file systems (map network drive)? That should be all you require. Just don't expect the same performance that you would get from files on local disk.

Yes, it comes with Version Control and is called, if I recall correctly, "Version Control.pdf".

But you CAN use Fmt() in a BASIC Transformer stage.

Shane means External Target, not External Filter. The command in the external target is a relatively straightforward awk command. Read the man pages on awk, or a good UNIX for beginners manual, for more information.

Even so, the non-key columns can have different names, and would then be reported on the output link.
I guess this is why the documentation also states that the Difference stage is being phased out, and is not to be preferred.

Stage dependencies are stored in RT_CONFIGnnn table for the job and, while the job is being designed, in DS_TEMPnnn. Structures for these tables are not documented.

That's a decision you need to make, and which you can ask your vendor. Business Glossary Anywhere is a really useful tool (access to your Business Glossary from almost any Windows application) but, if you don't need it, maybe you can save some money by not buying it.

What are the data types of the lookup keys? If string, are they equivalently trimmed?

Somebody, somewhere, HAS done some changes. Or there are syntax errors in your job, probably in Transformer stage.

What output ARE you getting?

There's no limit on the number of pivot keys - you just have to handle them all.

You don't need to add anything to the Palette - you can drag stages from the Stage Types branch of the Repository directly into a job design.

Change your "Lookup Failed" rule.

The after-job subroutine could look after that. But why write code when you have a perfectly good GUI? Certainly the after-job subroutine can capture the data, but it could also run a small job to write them into your audit table.

... or read C++ for Dummies or some equivalent introductory book.