PM31882: UNIX ONLY : LOCALIZED CHARACTERS USED IN TURBO INTEGRATOR PROCESSES ARE CONVERTED INTO UTF-8 FORMAT IN THE .PRO FILE

APAR status

• Closed as program error.

Error description

• Localized characters (like ? ? ? ? ? ? ?) used in Turbo
  Integrator Processes (for example in string variables) are
  converted into UTF-8 format in the .PRO file on the Unix side
  (tested on Solaris and AIX). This causes various problems. The
  showstopper for the customer is that when using an
  ExecuteCommand to export strings through the "echo" command, the
  resulting file is in UTF-8 format and another TI process is not
  able to read it correctly because the other TM1 functions cannot
  read UTF-8.?- Both admin server and TM1 server on Unix are
  running with ISO french locale (but no matter what ISO language
  is used) and the Language in tm1s.cfg is FRA (whatever it is).?-
  It seems to be a server runtime problem (independent from the
  Windows client) a there is the same problem when using CHAR
  function instead : ?CHAR(233) returns '??' instead of
  '?'?CHAR(224) returns '?' instead of ??CHAR(232) returns '??'
  instead of ???Sample code used
  :?sFileTmp='/cap-eiffel_2/home/seigneus/tests/test1.txt';?sLine=
  '?
  ? ?' ;?# does not work better with : sLine=CHAR(233) | CHAR(224)
  | CHAR(232) ; ?sCmd = 'echo "' | sLine | '" >> ' | sFileTmp
  ;?ExecuteCommand( sCmd , 1);??Opening test1.txt then shows UTF-8
  characters.??On Windows there is no problem as the .PRO files
  store these characters in ISO/ANSI format.?
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Users                                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IBM Cognos TM1 10.1.0                             *
  ****************************************************************
  

Problem conclusion

• Code Fix
  

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:

Fix information

• Fixed component name

  TM1 SERVER

• Fixed component ID

  5724W49SE

Applicable component levels

• RA10 PSN

     UP