DSXchange

The routines are supplied with DataStage. They are documented in the Routines branch of your Repository.

You really need an XML Input stage. XML Input stage reads XML and produces rows and columns; XML Output stage reads rows and columns and produces XML.

I guess keshav0307 read the section in the Parallel Job Advanced Developer's Guide that refers to environment variables, in particular the discussion of the APT_TERA_SYNC_DATABASE.

Visibility of generated OSH is configured in the Administrator client.

Each job is like an orchestra; there is one conductor process, one section leader process per node, and (assuming no combination) one player process per operator per node. In general, each stage generates one operator, but there are exceptions (such as the Lookup stage). By tracking the players' mem...

Search the forum. How you do this depends on whether a VOC pointer exists to the hashed file.

Welcome aboard! :D

I have not seen that behaviour, so tend to agree that it may have something to do with the manner in which your Oracle client software is configured.

All of them are relevant. It depends on what you want to accomplish. DataStage Engine (formerly UniVerse) is a full-functioned database and application development environment; that's why there are so many manuals (and, indeed, so many commands).

What is different between the two environments? Is the link row count actually zero on the second iteration in production? That is, is the loop exited validly?

That's only useful if you source dsenv prior to executing DS commands. It may be better to edit the .profile file.

Your export is not from a compatible version of DataStage for the version of DataStage into which you are trying to import it. This is primarily controlled by the ToolVersion setting. Newer versions of DataStage have newer components, that can not be imported into older versions; hence the prohibiti...

LIST.ITEM requires a VOC pointer. A VOC pointer can be created with a SETFILE command. Search the forum for details.

That APT_ORCHHOME is set in the Administrator module does not necessarily mean that it's set for you, the interactive user. You must make sure that it is explicitly set. You can prove that it's set using a set command.

There is a table called DS_AUDIT that records this information. It contains a nested table caled MODS that records the date/time and by whom modified. This post shows a couple of queries against that table.

New issue: new thread. Makes it easier for future searches.

Please begin a new thread.