DSXchange

Make sure that every load has a unique RunID which is part of every row loaded into the database.

DataStage had Version Control until version 7.5.

Information Server Manager in a near future release will be able to interact with source code control systems - directly with ClearCase and CVS, through an interface (API or Eclipse plug-in) to others.

Transformer stage code ends up being a callable object or callable function in a library (depending on how you link it). Its stage properties dialog has a Build tab where you can override the default compile and link options. The Build stage is the same, in that it generates callable objects. That's...

Please post all preceding warning/fatal messages. The one you posted is an automatic reaction to an earlier abort condition having been detected.

Pairs of Field() function for the first case, a single Field() function for the URL.

The Administrator is any user in the Administrators group, if the DataStage server is on Windows, or the user dsadm, if the DataStage server is on UNIX/Linux. If you tell us what's disabled we may be able to be of more help. For example, NLS is disabled if NLS is not installed or if NLS is installed...

Yes, parallel jobs too.

DSD.RUN is a generic "job starting" routine that also appears for parallel jobs.

Beware that ampersand is a special character for the shell. You need to escape or hard quote. For example:

Take node1 out of the default node pool (the one with "" as its name) - go back, perhaps, to naming a "conductor" node pool. This will push all processing onto node 2. To allow a controlled amount of processing to occur on node 1, design some (only a few) stage types to execute i...

You're failing to mention server1 in your configuration file. I believe (from your description) that you intended to name server1 as the fastname for node1 but named server2 instead.

There's no "otherwise" capability in the Switch stage. However, there's nothing special about a reject link except that you can't work with the Mappings (and it causes a message to be logged if it's used). You can set the If Not Found property to Output and direct these rows to the reject ...

Who told you that? It's unlikely. Changing EXACTNUMERIC ought not to affect applications catastrophically - it may give more significant digits as the result of calculations, but the target data type (precision,scale) should account for tidying that up. Other parameters in uvconfig being inadvisedly...

Do you have Runtime Column Propagation enabled? If you don't need it, disable it.

Import the COBOL copybook into DataStage. Then open the table definition, go to the Layout tab, open the Parallel option and (right click to) save the record schema in a file. Voila!

Could have lacked SELECT privilege to system tables where column information is stored.