DSXchange

To me, "keeping" in this context means "transferring into the result". Perhaps "using" would have been a better participle.

But not "keeping the decimal point". The Field() function never keeps the leading or trailing delimiter.

ssnegi wrote:Yes field function can be used to extract from a decimal keeping the decimal point as the delimiter.

Not true. Observe the solution, in which a decimal placeholder was explicitly concatenated.

You might get better answers posting on a Oracle forum such as AskTom.

Make sure to copy hashed files recursively (use the -r option with the cp command), since you must copy DATA.30, OVER.30 and .Type30 files). Probably the fastest way to refresh TEST from PROD is to discard the TEST environment and start by creating a new one. Next best is to be selective about what ...

My earlier code assumed (incorrecly) that there was a colon between the string and the next time. The code can be changed to account for that - I leave it as an exercise for the reader, with the hint that you discard that part of the string already processed each iteration through the loop. As for y...

To clarify, the "suppress_zero" option removes only non-significant zeroes; that is, those to the left of that part of the decimal number to the left of the decimal placeholder and those following any non-zero digits to the right of the decimal placeholder.

Table Action = Replace will both drop and create the table, without checking whether metadata matches the existing table. It does not fail if the table does not already exist.

I don't believe there is any way to change default property settings in out-of-the-box stages (in general - though the Sequential File stage does allow default format to be selected).

Why not use an External Filter stage?

The ODBC API is published by Microsoft Corporation. I'll have to research the link to developerWorks - don't have it with me.

Welcome aboard. The short answer is Yes. Use stage variable to indicate whether you are in a detail row or not, initialized to @FALSE. Set the stage variable to @TRUE when the previous row (preserved in a later stage variable) contains BEGIN DATA, and set it to @FALSE when the current row contains E...

The engine-side compile should be dscc

That's better, but the layout doesn't really jump out at me that actual_Sequence is in the loop (which I missed first time too). Perhaps a layout like this would make it clearer. ExtractBUNames ----> StartLoop <--------------- EndLoop | ^ | | V | uvBUName --------> NestedCondition | | V actualSequen...

That's not obvious in your master sequence design. At the very least more information (Annotations) required. Why do you want to "do nothing" a number of times? This too is not clear.