Decimal information lost when using the CHOOSE() function

Technote (troubleshooting)


Problem(Abstract)

WebSphere® Transformation Extender has the potential for changes of numeric data values when using the CHOOSE() function on decimal numbers with a comma as decimal delimiter.

Symptom

When the input has a repeating item within a group defined as decimal numbers there are two ways to reference these numbers:

=NumberItem[5]:In1
or
=CHOOSE(NumberItem:In1,5)

Both will get the 5th iteration of the repeating object, though CHOOSE() is preferred, because the second argument can be a reference itself, and does not need to be hardcoded in the rule:

=CHOOSE(NumberItem:In1,Index)

However, if NumberItem is a decimal, and the decimal delimiter is a comma, some of the data will be lost and/or changed. For example, the following input:

5,98
4,12
0,13

...will be converted to:

5,
4,
13,

...if using the CHOOSE() function to map these objects.

This does not affect any decimal numbers with the decimal delimiter defined as a dot.


Cause

This has been identified as a product defect under APAR PM77034

Diagnosing the problem

Decimal numbers losing the non-whole part.

Resolving the problem

Obtain and apply APAR PM77034

Product Alias/Synonym

Ascential DataStage TX

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Transformation Extender
Core Engine

Software version:

8.2, 8.2.0.0, 8.2.0.1, 8.2.0.2, 8.2.0.3, 8.2.0.4, 8.2.0.5, 8.2.0.6, 8.3, 8.3.0.0, 8.3.0.1, 8.3.0.2, 8.3.0.3, 8.3.0.4, 8.3.0.5, 8.4, 8.4.0.0, 8.4.0.1, 8.4.0.2, 8.4.0.3

Operating system(s):

AIX, HP Itanium, HP-UX, Linux, Linux zSeries, OS/390, Solaris, Windows, z/OS

Reference #:

1618007

Modified date:

2012-11-20

Translate my page

Machine Translation

Content navigation