DSXchange

Search DSXchange for more. DataDirect drivers that ship with DataStage are licensed only for use with out-of-the-box stage types (mainly ODBC and RDBMS using ODBC), but give a 15 day grace period to other use. Your grace period (from first use) has now elapsed. If you are only using stock-standard ...

Check the included header files? EQUATE declaration? (I don't have any restartable sequences at the moment, so can't check.)

Hello Sir Do you mean to sya that QS v8.x comes with lot of bugs? As far as I am aware there is no-one in my part of the world yet using QualityStage version 8.x, at least not in anger. Some POCs (proofs of concept) are about to happen, however. Could be interesti ... Two years on! And there's noth...

The only stage I've seen that supports transaction grouping is the ODBC stage in server jobs.

Version 7 is pre-IBM so you're being a trifle unfair. The only available "solution" without an export in version 7 is a query against the Repository tables, particularly DS_JOBOBJECTS (and probably DS_JOBS for filtering by job type).

Please advise your precise version (for example 8.0.1). There seem to be some issues with the executing user in versions 8.0 and 8.0.1.

dspxlearn wrote: So, for long term backup should we load them to sequential files eventually?

Not necessarily. Database tables serve just as well.

Consider the string "". This is not null, and has a length of zero.

cp$dtm is just a variable name. You can find its assignment statement earlier in the job control code.

DLam wrote:So you are saying that if I make the table metadata a "shared" repo, IDA/RDA should be able to go out and touch it?

Yes

Either set environment variable APT_DISABLE_COMBINATION or disable operator combination in particular stages (on the Advanced tab).

Investigate whatever operator is named in the error message.

How about you provide detail of log events 9, 10, and 11, as you were asked to do?

You don't. You can capture the result and run a DataStage job to put it in a column. How about you provide a written specification of what you want to do? Ignore PL/SQL, ignore routines - do it in English. Alternately you can write a whole lot of functions that employ the ODBC API (called BCI functi...

Server routines are written in DataStage BASIC, not in PL/SQL or any other scripting language. The return value is returned through a variable whose name is Ans. It is also possible to use user-definable system variables such as @USER.RETURN.CODE and @USER0 through @USER4 to return other values. Tec...

This is very easy with MatchField() functions and concatenation in a BASIC Transformer stage.

If you know that there are always four characters before the first underscore, then there is a solution using Index() and substrings.