DSXchange

Restarting the server won't help at all. If you use an array of 24000 and the database server generates 24000 warnings, then DataStage will log all 24000 warnings. That's the DataStage philosophy; if you need to know about it, it will be logged. The way to remedy the situation is to prevent the warn...

A training class Programming with DataStage BASIC is available.

Welcome aboard. :D The sparse lookup is recommended when you know in advance that very few distinct values will be looked up - how many rows are in the database table is actually irrelevant. If this condition does not obtain, then sparse lookup is probably not to be preferred - contemplate pre-loadi...

In server jobs the answer is yes; for parallel jobs I don't know. Why not try it and let us all know?

That's right - they're incompatible. What did you expect?

You can install multiple versions of the server (this post) and you can install multiple versions of the client (search for details) using the multi-client manager to switch between them.

Source code for all four is supplied - why not inspect it? The non-silent ones log an entry in the job log, the silent ones don't. That's the difference.

The default PRECISION in DataStage is 4. The only way you can change this is to perform your calculation in a Routine, in which a PRECISION statement appears to change that value. FUNCTION DivideByThree(Arg1) PRECISION 9 Ans = Fmt((Arg1) / 3, "MR9") RETURN(Ans&#...

The encrypted string is always composed of printable characters. That is why this approach will work.

Nothing you can change in uvconfig will affect your flooding of the machine with too much work.

The Install and Upgrade Guide has this information, and you can search this forum for more.

You need to allocate different memory keys if you want both versions to be simultaneously operable.

It means that, on row 1, there are fewer columns in the file than are specified in the column definitions.
You must get this right. It may be a badly-specified delimiter character.

With an array size of N you can get back a buffer containing N warnings. You can not prevent this. It's one of the down sides of using arrays.

And the important point is that this was done in a Transformer stage (not, for example, in a Modify stage).

Change the column name in an upstream Modify stage.

Two Lookup stages will work. A differently constructed Lookup File Set (similar to hashed file) will probably also work.

MKS Toolkit.