IV07994: MSG SLOT WITH DBCS CHARACTERS NOT BEING ADDED TO EVENT SENT FROM TEMS.

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)

APAR status

• Closed as program error.

Error description

• Problem Description:
  
  When certain DBCS charsets are in use, the message
  EIF message slot for events being sent from the TEMS is not
  populated.
  
  It was seen that message slots with DBCS characters were not
  being added to the EIF event being sent from the TEMS to an EIF
  receiver.
  
  This was seen for an ITM 622 TEMS at the following level:
  
  Environment:
  
  Component: kds
  Driver: tms622mdx:d0249a/4067831.4
  Timestamp: Sep  6 2010 16:02:08
  Target: lnxx86-l23-g33
  KDS Server   Version: 622  Build: 10249
  Driver: 'tms622mdx:d0249'
  Date: Sep  6 2010  Time: 16:02:08
  build date: 'Mon 09/06/10' info: kms/kds prod ne
  
  Detailed Recreation Procedure:
  
  1> if Locale is set to en_US.*,  msg slot including
  chinese chars can be displayed correctly at the EIF receiver.
               .
  2> if locale is set to zh_CN.UTF-8,  msg slot including
  chinese chars can be displayed correctly at the EIF receiver.
  
  3> if locale is set to zh_CN,  ZH_CN.gbk, zh_CN.GB2312,
   any msg slot including chinese chars is blank at the EIF
  receiver.
  
  4> if locale is set to zh_CN.gb18030, one of the factors
  deciding whether the msg slot is seen,
  is the number of characters in the string.
  
  Related Files and Output:
  Logging from debug-enabled builds of KFAOMTEC are available on
  ECURep in this PMR's directory.
  

Local fix

• Some languages have more than one character set, for
  example zh_CN.GB18030, zh_CN.GB2312 and zh_CN.UTF-8.
  
  Changing to another charset for the same language has been seen
  to mitigate the issue.
  

Problem summary

• A message slot with DBCS characters is not added to the event
  EIF message slot for events being sent from the management
  server.
  
  If a slot mapping contains DBCS characters and the hub
  monitoring server locale is not en_US or UTF8 but is the local
  locale, the value may not get added to the event.
  

Problem conclusion

• The EIF forwarding now copies data directly into memory instead
  of processing it like a string.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
    | fix pack | 6.2.2-TIV-ITM-FP0007
    | fix pack | 6.2.3-TIV-ITM-FP0001
  

Temporary fix

• Set locale to en_US or UTF8
  

Comments

APAR Information

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

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

  OA38233 IV11598 OA38946 OA39004

Fix information

• Fixed component name

  TEC GUI INTEGRA

• Fixed component ID

  5724C04TG

Applicable component levels

• R622 PSY

     UP