DSXchange

With Information Server, even four-tier is possible.
Client <----> DataStage Server <----> WAS <----> IIS
WAS = WebSphere Application Server
IIS = IBM Information Server

A possible approach, without giving the problem a great deal of thought, might be to encapsulate all the "pass through" columns into one (delimited string). You could then decompose that string downstream.

No. Commit is commit. This calls for "recovery" design. You need to identify which rows were committed in the earlier jobs and delete them. This will also be transactional. Theoretically you could start an outer transaction at the beginning of the job sequence and issue a commit at the end, but you ...

Before anyone wastes their time with that, can you give any reasonable scenario for wanting to change the name of any of those constructs except sequential files?

The short answer is No. View Data takes everything through another layer of mapping (the UNIX-to-Windows bit, specified by your "...-CS" map and any assumptions that the Windows controls used in the data browser may be making). My experience with using View Data is that you see a lot of "unmappable"...

Your assumptions are awry, as I illustrated in this thread Forget UniVerse - it's a totally separate product (owned by IBM and used by literally millions of customers world-wide). DataStage and UniVerse parted company in 2000 with the release of DataStage version 6.0. DB2 (or Oracle or SQL Server) d...

So you code around that possibility.

Every single routine has a different purpose. Helper subroutines have "DSR" suffixes because (I believe) they affect the DataStage Repository. UniVerse Database is no longer existing in the DataStage Engine from DataStage v6.0. The database from that point has been called DataStage Engine. It remain...

1. They are most readily differentiated by prefix ("DSD" versus "DSR") and by location ("DSD_BP.O" versus "DSG_BP.O").

2. That would be a clear violation of your end user license agreement.

3. I dispute your "obvious absence" assertion.

You could use external source, but it's probably easier to use a Filter command in the Sequential File stage. Your unzip command's output is piped directly to the "input" of the Sequential File stage (that is, no unzipped file appears on disk).

I challenge you to find anything more efficient than what I suggested.

What we usually expect is that you post a message indicating how it was resolved when marking a thread as Resolved. That way future searchers will have a better idea of what to look for.

Please do the needful.

An alternative, where you don't need a lot of complexity, is to use a Hashed File stage with the hashed file type set to 19. In this case the Key column becomes the file name in the directory, and the non-key columns become the file contents; the type 19 "hashed" file is, in fact, an operating syste...

There will at least be an informational message showing the actual command to be executed (with job parameters resolved). Can you check that, and post what you see there? If there is no such message then the logic of your job sequence is such that the Execute Command activity is not being invoked, s...