DSXchange

A following Transformer stage would seem to be the easiest. And/or a build op if you're into coding of these beasts. The build op gives you greater flexibility in handling out of range values (precision 22 may not handle all Double numbers).

In the Find capability in the Data Browser, it would be nice to be able to find the next occurrence not equal to a value in a particular column. For example, for the current selection a column may appear to have all zeroes. I'd like to be able to find the next non-zero value, without having to speci...

Welcome aboard! :D Getting the current maximum value from the database is the only totally safe way. Some advise the code-based solution you propounded; others suggest using a DataStage job to load the result in to a hashed file. The advantage of this approach is that you can have a separate record ...

No.

(Can't get more direct than that.)

Of course, Michael's solution only works if DW_BATCH_CONTROL is a UniVerse table! As I noted earlier, I suspect that this would not be the case in one of Peter's implementations.

Using an external editor, determine whether this particular value contains any non-printing characters, such as Esc. You (as a human) won't be able to see them, but they can cause a lookup to fail.

Welcome aboard! :D The answer is to use a specialized plug-in (= optionally installed) stage that generates ABAP code and uses either RFC or FTP to get that code executed within SAP R/3. Talk to your supplier about the "SAP Extract PACK", which contains the requisite stage types. There is an additio...

You "solve" it by not breaking the rules. A Transformer stage can have at most one stream input link. All other inputs to a Transformer stage are reference inputs. The Sequential File stage does not support "get row by key" functionality, which is why it reports "source stage does not support refere...

It seems to work properly in the ODBC stage. :D

If DW_BATCH_CONTROL is a hashed file (or UniVerse table) it's really easy. I suspect it's not, however. The "least code" approach is to have a small job perform the SQL capturing the result into a text file, then "read" the text file. Sufficient would be Call DSExecute("UNIX", "he...

I agree with Ken's diagnosis; if you - or someone else - has removed the .Type30 hidden file, then DataStage has no way of knowing that the directory is supposed to be a dynamic (Type 30) hashed file. Therefore DataStage treats the directory as a directory (Type 19) file. [Type 1 requires a hidden f...

Welcome aboard! :D The folder stage has a maximum of two "columns". The first gives you the file name, the second contains the file contents. You should not be trying to put these in to a single sequential file. Lose your first Sequential File stage. Pass directly through to the Transformer stage, i...

Welcome aboard! :D Please try to use a meaningful subject; it helps when later you - or anyone else - is searching for answers. The DataStage log is already in a table. Search for RT_LOG; somewhere you will find the column definitions. Create a DataStage job to extract entries from the DataStage job...

UniChar() is only possible if NLS is enabled. Otherwise it internally invokes Char().

If your customer is still having DWord problems, get them to investigate the "string math" functions SADD, SSUB, SMUL and SDIV. Unlimited precision.

The problem is twofold. First, it's not a file, it's a database table (called DS_METADATA) that holds table definitions. Second, the metadata for DS_METADATA are deliberately not completely defined, so that you do not have column names via which to effect an UPDATE statement. IF you knew the record ...