DSXchange

From the operating system (perhaps through ExecDOS) you can redirect the output of dsjob -logsum command. Or you can create your own routine using functions from the DataStage API to interrogate the log.

You could use Ereplace() in a Transformer stage downstream of the XML Output stage.

FastTrack uses a five-part fully qualified name containing the host name, data source, data store, data schema, table name. Search DSXchange for more information - this has been addressed within the last month.

You can always use UNIX commands from the DataStage Administrator client using the SH command. For example

Transformer stage.
Copy stage. (You will still get the warning.)
Modifying the source metadata.

Moderator: please move to Server forum

Moved. I'm thinking it should really go in General since this topic applies to both products but since I've added notes about Server job access, we'll go where you bid.

karthi_gana wrote:It works fine.

This means that it's correct.

You need to find where osh_wrappers is, and amend PATH appropriately. Or it may be that your installation was not successful. What does the History section of Version.xml (in the DataStage installation directory) tell you?

Check the job log. What is the value of the PATH environment variable?

What are the stage types in your design?

To complete what Craig surmised, res stands for "resolution", a coded value for how to resolve deadlocks in the "UniVerse" database (you can kill the process with the newest-begun transaction, you can kill the process with the fewest locks in a transaction, you can kill one of th...

There's a file in the DSEngine directory called dsdlockd.config. In here you can configure the daemon to start automatically when the engine starts.

In the toolbar of the Designer client.

I suspect that the default is because people don't take enough care with partitioning then complain that "the result is wrong". The same will be true with the PXPivot stage - you need to have the data partitioned on the pivot key, using a key-based algorithm.

Unless you've spent lots of money on dedicated sort utilities like SyncSort or CoSort, the tsort operator in DataStage is quite effective, usually able to perform better than the UNIX sort command. I prefer to use an explicit Sort stage rather than input link sort, so that I get greater control over...