DSXchange

dsjob began life as an example of how to program using the DataStage C API. Note that it is a C program, not a C++ program. From memory (since I'm not in a position to check) complete source code was provided in the programming manual, and on disk in the sample directory.

But it only works if the job handle is valid, resulting from an earlier successful invocation of DSAttachJob() or use of DSJ.ME.

It was not always the case. Shared (READL) locks used to be implemented differently. Nowadays they are implemented as wait lists that queue in much the same way (and on the same number of semaphores) as the exclusive (READU) locks.

Go to the next Rocket Software U2 University to learn more.

How is ParallelJob_handle allocated its value?

U didn't ask the question.

The second person personal pronoun in English is spelled "you".

U is one of our posters.

... once you're competent with the language, the classes that you will need (the DataStage API) are documented in the Programming DataStage manual.

Why not just use the Slowly Changing Dimensions stage?

You shouldn't need to remove the dashes. However, since YMD is not your default locale setting, you need DYMD in the Iconv() function. Also, it's a space, not a dot, in the G conversion. OConv(IConv(DSLink1.LOG_DT_TM, "G0 1" : @VM : "DYMD"), "DMA" : @VM :"MCT")

From memory it's to be found in the sample directory.

MAXRLOCK must always be (RLTABSZ - 1). That may have something to do with why the first uvconfig settings gave problems.

It really depends what you mean by "some way" but, in general, the answer is no. Rule Sets are stored in text files so, if "some way" is this identical format, then all you need to do is to emplace them correctly and make sure you have at least the mandatory files (classification...

I think you've encountered a bug. The File Name column works properly in some versions, not in others. Without knowing your exact version it's hard to say. Involve your official support provider.

Please note that Craig requested the version of the Oracle client, not the DataStage client.

This might do it for you, then.

Then you should be OK. Failed lookup rule should be set to Continue, in which case any column mapped from the reference input link will be NULL if the lookup failed. There is an option for returning more than one row from a lookup, should you require that.