DSXchange

You get the basic tools to map EDI with DS TX. It is possible with EE alone, but you would most likely have to write a lot of customer Pcode. You map to X12 standard, you would also purchase a set to "Type Tree" which are predifined data structures for the ANSI standard. In the Map Designe...

EDI translations was the original purpose of DataStage TX, way back when it was TSI. It is known as an any to any transformation engine.
It runs as a Stage on DataStage and EE 7.5.1. Depending on what you need to do, you may or may not need DataStage, TX EE is a realtime environment on it's own.

Unless you use burst mode. Then you can commit by burst. You can also set up the map to send all good data to the DB and bad data to a file.

Being that NT is such a stable, robust and secure OS, I can't see why anyone would not want to continue to support it.

TX can handle bulk loads too. There is a "burst" mode that allows you to get a predefined number of rows, so you don't hit any environmental limits. MapStage under PX should be an interesting creature. Haven't tried to test this yet myself.

TX is an advanced transformation engine that can handle complex data types with ease. It can also connect to a variety of messaging programs, databases and other apllications. It can be used with Event Server, to be time and or event driven with coordination between time & event, or even multipl...

Use reuse work area for lookup type files that don't change. This is for maps running under the Event Server.
If you are using 6.7 or higher and have memory issues, it could be a leak, or your map page size & count settings could be too high.

It's in the documentation, unless you mean the UNIX returns.

Or wait for 8.0 and use the debugger.

TX is still the same (improved with 7.5.1 and 8.0 beta). What should be appreciated is MapStage, allowing DS users to use all the built in functions and the ability to handle even the moxt complex data structures.