DSXchange

Yes, I do, though primarily wearing my UniVerse hat rather than my DataStage hat.

You can find a well-documented example, a function to execute any DML statement, here

81002 can also occur if the dsrpcd daemon is stopped.

81002 decodes as "dsrpc: No connection."

Just put the call to DSLogWarn within the scope of CASE @TRUE (and make sure that Ans is assigned some value that can be handled by its caller, perhaps @NULL or -1.

On the link that reads from the hashed file specify for read cache "disabled, lock for updates". On the link that updates the hashed file (which ideally should run out of the same Transformer stage, so that it's guaranteed to be done in the same process) do not check the "write cache" box. I don't t...

It appears that there is some kind of problem with DataStage finding the compiler. Search the forum for an exact match on exit status 256.

I doubt it very much.

This error message usually arises when you have asserted on the input link of an Aggregator stage that the incoming data are sorted and it turns out that they are not sorted, or not sorted in the order you have specified. Asserting "sorted" on the Aggregator input does not cause sorting to occur; it...

Suggest away, David. You get MKS Toolkit with DataStage 7.5 on Windows. So you can do UNIX stuff.

How about a 26 row x 2 column hashed file, setting the result to "D" if the lookup fails?

None at all.

$DSHOME/bin/analyze.shm -d

Welcome aboard.

If you have questions about parallel jobs please post on the parallel forum.

By default the maximum precision of DECIMAL is 15 (see PRECISION statement in the DataStage BASIC manual, though it claims 9).

Try using FLOAT as the data type. You might also change the uvconfig parameter EXACTNUMERIC to get more precision.

Not out of the box. It can be done with Oconv() using "MX0C" (or possibly "MB") conversion and rearranging the pairs of bytes.

SELECT (case when a.DUP_IP_ID is null then a.IP_ID else a.DUP_IP_ID end) || b.NM || b.AR_ID || b.CLS_BAL || b.CNRL_BNK_IDY_CL_ID || c.AR_PPS_TP_ID || b.AR_X_IP_TP_ID FROM ... The || operator performs concatenation in SQL. It's nothing to do with DataStage. If you want to concatenate the columns with...