IT11216: TRANSLATION ATON() WILL NOT SILENTLY ACCEPT COMMA AS DECIMAL

si_52_build_5020500_interimfix_9
si_52_build_5020500_interimfix_9

APAR status

• Closed as program error.

Error description

• As part of a code fix in V5.2.5 will no longer implicitly
  accept a comma as a decimal separator in the ATON() function
  during translation. It did accidentially in 5.1 up to 5.2.4,
  which was fixed. Please note that reading data into the map and
  specifying the comma as separator in the map or via the
  business process always worked and continues to, for
  examplem for positional or EDI.
  The same applies to the SWIFT format reader which
  continues to accept the comma.
  

Local fix

• Make sure that the data is read correctly into a real variable.
  This can be done by explicitly specifiying the comma
  (positional or EDI) or by using the right data types (SWIFT).
  If you need to convert then replace the comma with a dot before
  you call the aton() function in the extended rule.
  

Problem summary

• Users Affected:
  Customers who use standards enveloping, translation and
  mapping
  
  Problem Description:
  ATON() fails in V5.2.5, while it works in V5.2.4.2
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  As of V5.2.4.2, the translator no longer converts a comma to
  a period by default. Customers who want this conversion need
  to add the parameter "storage.customerDefaultDecimalSeparator"
  to the transation.properties
  file, which tells the translator what character to
  consider as decimalSeprator.
  
  Delivered In:
  5020500_9
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

•    TRANSLAT
  

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels