DSXchange

Having multiple links into the one database stage will cause all those links to form a single transaction. Set your transaction size (and array size) to 1.

Can you use Run Director from the Designer's Tools menu?

Welcome aboard.

Are you logged in as a LOCAL administrator? (Being a domain administrator is not good enough.)

Return value is the exit status.

You probably need to test the value of $CommandOutput activity variable.

You could use a design something like this. Use constraint expressions within the Transformer stage to direct records to the output links depending on whether they're insert, update or delete records. +---------+ +-------------+ +-----------+ | | | | -INS->| | | | | | | | | SeqFile | ----->| Transfo...

Just for laughs, what happens if you put a copy of your operator executable into RT_BPnnn.O directory?

Short answer: no.

You could try search and replace in a DSX or XML export, but be very careful to change only the values that need to be changed.

Are you actually running DataStage jobs from which information can be collected?

There are not even any overheads when running multi-instance jobs. The only overheads occur when viewing the job log (effectively a view is needed that selects only the entries that relate to a specific invocation). Existence of an instance is recorded in RT_STATUSnnn so there's a tiny overhead (two...

How about putting your library at the beginning of LIBPATH?

This may seem counter-intuitive, but try including the parent directory in the command search path (PATH) also. Try also setting it into LD_LIBRARY_PATH (yes, I know AIX is not supposed to use that one, but I've encountered it in the past). And, of course, check the value of LIBPATH in the job log e...

Existence of the file is more easily checked using the test command in an Execute Command activity in a sequence. Validity as CSV can be done in any of the ways we've already suggested, as well as operating system commands (such as grep for any lines that do not contain any commas, piping the output...

You imported the metadata as a global task (not within the scope of a project). Before you can analyse anything, you must go into your Project Properties and "register interest" in some or all of the imported metadata. Only then will table definitions become visible in the Column Analysis ...

If the diagnostic routines within the product can only throw an "unknown error" how would we be expected to do any different? One could surmise that, to retrieve data, an SQL statement has to be built. The fact that you are retrieving data indicates that that is succeeding, so the error me...

It is exceedingly unlikely that they will ever change this mechanism. If you can generate a business case, feel free to submit a product enhancement request to IBM. For a small and finite number of jobs, you could create a sequence with (for example) a Nested Condition activity that causes the appro...