IT20836: MONITORING BITSTREAM NOT INCLUDED WHEN HTTP HEADERS MQ BASED MESSAGE THAT CONTAINS UNICODE CHARACTERS

APAR status

• Closed as program error.

Error description

• When a message is retrieved by an MQInput node a message tree is
  created that contains MQ related parsers (MQRoot, MQProperty
  and MQ headers).
  In a compute node a new HTTP message tree can be created by
  creating HTTP headers and copying the message body to the
  OutputRoot message tree. Although this is primarily a HTTP
  message the underlying message is still related to MQ. As such,
  if a monitoring message is serialized from a such a tree the
  HTTPRequest header can influence how the message body is
  serialized. Specifically the monitoring message body will be
  serialized in the queue managers codepage. If the monitoring
  bitstream contains unicode characters then BIP2136E/BIP3914
  exceptions will be observed in the service trace and no
  monitoring bitstream will be included in the monitoring message.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus converting MQInput to HTTP
  messages.
  
  
  Platforms affected:
  MultiPlatform, z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a message is retrieved by an MQInput node a message tree is
  created that contains MQ related parsers (MQRoot, MQProperty and
  MQ headers).
  In a compute node a new HTTP message tree can be created by
  creating HTTP headers and copying the message body to the
  OutputRoot message tree.
  Although this is primarily a HTTP message the underlying message
  is still related to MQ.
  As such, if a monitoring message is serialized from a such a
  tree the HTTPRequest header can influence how the message body
  is serialized.
  Specifically the monitoring message body will be serialized in
  the queue managers codepage.
  If the monitoring bitstream contains unicode characters then
  BIP2136E/BIP3914 exceptions will be observed in the service
  trace and no monitoring bitstream will be included in the
  monitoring message.
  

Problem conclusion

• The product has been corrected such that the HTTP request
  headers do not influence how the message body is serialized.
  As such the monitoring message bitstream is successfully
  included in the monitoring message.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.10
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  INTEGRATION BUS

• Fixed component ID

  5724J0540

Applicable component levels

• RA00 PSY

     UP