PI27313: ABEND 878 14 WITH ERROR MESSAGE +CSQX112E XXXX+ CSQXDISP DISPATCHER PROCESS ERROR TCB=YYYYYYYY REASON=878000-00000

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• ABEND 878-00000014.
  In the CHIN job-log, there was CSQX112E error message.
  .
  +CSQX112E XXXX+ CSQXDISP Dispatcher process error, TCB=yyyyyyyy
  reason=878000-00000014
  .
  From the slip trap of the 878 abend, you can see the
  cause of the S878 abend.
  The Receiver channel xxx.yyy.zzz has received a
  message from the partner which is incorrectly formed.
  The MQMD of the message indicates that the message body
  starts with an RFH2 header. However, the message body
  starts with '....XC1_ERROR'. The message is destined for
  MY.REPLY.QUEUE, but the MQPUT to the queue by the
  receiver channels fails with MQRC 2142, MQRC_HEADER_ERROR,
  as expected.
  The message is then put to the dead-letter queue by
  rriAddDLQMessage.
  The message specifies MQRO_EXCEPTION so rriAddDLQMessage
  then tries to put an exception report to the ReplyQ.
  This requires the length of the message minus the message
  headers to be calculated.
  However, due to the incorrectly formed message an incorrect
  length value is calculated which results in the S878 abend.
  
  Additional Symptom(s) Search Keyword(s):
  ABEND878 ABENDS878 S878 S0878
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
  *                 Release 0 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: A malformed message, specifying a       *
  *                      header format without a valid header,   *
  *                      with exception reports, being put by a  *
  *                      receive channel may result in an abend  *
  *                      S878 shown by message CSQX112E.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The put of the malformed message by the receive channel fails
  with MQRC_HEADER_ERROR, MQRC 2142. An example of such a message
  would be a message with RFH2 format, without a valid RFH2 in the
  message data. This then results in the message being put to the
  dead letter queue and the exception report being generated.
  During the processing for the exception report, the length of
  the headers is calculated, which results in an incorrect value,
  due to the message data being read as the structure length. This
  can result in the length of headers in the message being
  calculated as an extremely large or negative value. This can
  result in the abend reported during processing for the exception
  report message.
  

Problem conclusion

• Processing for exception report messages has been updated, to
  check the calculated length of headers in the original message
  to ensure an appropriate value is used in this case. This allows
  the exception report to be successfully put with no abends.
  

Temporary fix

Comments

APAR Information

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

  PI24627

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

  UI23074

Modules/Macros

• CSQXRMMQ
  

Fix information

• Fixed component name

  WMQ Z/OS 8

• Fixed component ID

  5655W9700

Applicable component levels

• R000 PSY UI23074

     UP15/01/29 P F501

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.