DSXchange

One definite con for the "same server" approach, which a couple of my clients encountered, is that all development has to stop if any heavy duty testing (such as performance testing) is contemplated. They committed the additional booboo of underconfiguring their non-production environment.

80011 usually means that the DSRPC process is not running or is unreachable.

Check whether dsrpcd is running. If it is, check whether port number 31538 is open through any firewall that you may have.

Latest Data Direct ODBC drivers are available from Fix Central.

It could be that someone has removed the special numeric code from your .odbc.ini entries, the code that the Data Direct drivers use to ascertain that a properly licensed driver is being used.

The dsjob command takes multiple occurrences of -param name=value

So your paramlist variable will contain something like

Do some research into "units of work" and "Waves" in DataStage. CDC does not naturally split what it retrieves into units of work.

Maybe you would also like to know that there's a manual called the Parallel Job Advanced Developer's Guide, plus a whole heap of good technical documentation on developerWorks, plus a number of RedBooks dealing with various DataStage topics.

For financial things prefer the commercial side of DSXchange; that is, dsxchange.net rather than dsxchange.com. For example editor@dsxchange.net

Why can't you use a Column Export stage? It's inputs are defined by RCP, you can name a single column for its output without violating your overall requirement for RCP as this column will function dynamically.

No changes to how parallel routines are implemented. The ONLY guaranteed way to "convert" server routines to parallel routines is to reverse-engineer the logic of the routine into a set of algorithms (a manual process) then write the C++ code to implement those algorithms (another manual t...

There are many options to generate the XML source column, including populating the column from DB2 directly, or using a Column Export stage, or using a Transformer stage.

The dsjob command serves as an example of how to use the DataStage API. You may as well use dsjob, as it's supported, but my point is that you can create your own.

My previous project used the check-in/check-out capabilities exposed in Information Server Manager to interact with SubVersion. Developers had to be trained to use this mechanism universally, and there was some management overhead monitoring compliance.

You might like to tell us which stage type you've chosen to use.

It would also be particularly useful to tell us which columns you have designated to be Key.

Why not just get Metadata Workbench to effect a search filtered on date/time modified? You can turn the result of this search into a report.

The default for DataStage encrypt is AES-128.