IT14025: IIB V10 FAILS TO PUT A MQ MESSAGE EXCEEDING 4MB WITH REASON 2010- MQRC_DATA_LENGTH_ERROR

APAR status

• Closed as program error.

Error description

• An IBM Integration Bus Version 10 message flow using an MQ
  Output or MQ Reply node, fails to put a MQ message that exceeds
  4 MB (4194304 bytes).
  
  A BIP2667E message reports a MQ return code 2010
  (MQRC_DATA_LENGTH_ERROR) when IBM Integration Bus Version 10
  attempts to put a MQ message exceeding the default 4MB maximum
  message length (MAXMSGL) to a queue. This occurs even when the
  MAXMSGL has been configured to exceed 4MB on the queue manager,
  channel and queue.
  

Local fix

• The limitation is not experienced if a Client Channel Definition
  Table (CCDT) is used instead of specifying the connection
  parameters on the MQ node/policy, because the MAXMSGL value for
  the client connection can be specified.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM Integration Bus Version 10 sending a MQ message
  greater than 4MB using client connections configured on a MQ
  Output or MQ Reply node explicitly, or using a policy.
  
  
  Platforms affected:
  z/OS, MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A BIP2667E message reports a MQ return code 2010
  (MQRC_DATA_LENGTH_ERROR) when a MQ Output or MQ Reply node
  attempts to put a MQ message exceeding the default 4MB maximum
  message length (MAXMSGL) to a MQ queue.
  
  IBM Integration Bus Version 10 can be configured to use a client
  connection between a MQ node (client) and a queue manager
  (server) using a channel. If the client connection is defined by
   configuring the connection details on the MQ node or using a
  policy, the client connection object's maximum message length
  (MAXMSGL) is always set to the default 4MB.
  
  When a MQ node in a message flow initiates the connection to the
  queue on the queue manager using the channel, the maximum
  message length is negotiated between the client-connection and
  server-connection objects and the lower of the two is used.
  Therefore even if the maximum message length has been configured
  to exceed 4MB on the queue manager, channel and queue, the put
  of a message exceeding 4MB will fail with return code 2010
  (MQRC_DATA_LENGTH_ERROR) because the client side setting is
  always 4MB.
  

Problem conclusion

• The maximum message length (MAXMSGL) for the client-connection
  object used by the MQ Output and MQ Reply nodes in IBM
  Integration Bus Version 10 has been set to the WebSphere MQ
  maximum limit of 104,857,600 bytes or 100MB. This will allow the
  channel negotiation step in the client connection to set an
  appropriate maximum message length for the communication,
  depending on the lowest value set on the queue manager, channel
  and queue.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.0      10.0.0.5
  
  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