PI57299: WMQ Z/OS :MQMD.EXPIRY=0 PREVENTS MESSAGES TO BE ROUTED TO DEADLETTER QUEUE AND RESULTS IN MQRC=2013 16/02/11 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Failed to PUT the message into the dead letter queue due to
  MQRC2013,following error messages were displayed in syslog:
  16:52:15.10 CSQ2004E +CSQ1 CSQ2PUTD ERROR USING QUEUE 390
  CSQ1.DEAD.QUEUE, MQRC=2013 (MQRC_EXPIRY_ERROR)
  The PI42711 added MQMD.Expiry=0  code in CSQ2MTOO,which
  introduced in MQRC2013.
  .
  After the CSQ2004E message the IMS Bridge queue is closed
  and processing needs to be restarted by get-disabling and
  enabling the queue.
  

Local fix

• n/a.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: After application of UI31498, an IMS    *
  *                      bridge request message, with an expiry  *
  *                      value, which cannot be processed by IMS *
  *                      may result in message CSQ2004E with     *
  *                      MQRC 2013 (MQRC_EXPIRY_ERROR).          *
  *                      Additionally, with expiry and report    *
  *                      options specified CSQ2004E message may  *
  *                      be followed by abend 5C6-00F20058.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a IMS bridge message cannot be served by IMS, such as a
  stop transaction being used by a request message resulting in
  message CSQ2001I with sense code 001A0019, the request message
  will be put to the DLQ. However after the application of
  UI31498, if the message has an expiry interval set in the MQMD
  of the message, the process to DLQ will result in message
  CSQ2004E with MQRC_EXPIRY_ERROR. This is due to the fix in
  UI31498 setting this value to 0 when the field is not
  MQEI_UNLIMITED, which is not expected in the DLQ process,
  resulting in the CSQ2004E error.
  
  Additionally when COA type report options are specified on the
  request message, the same incorrect expiry value results in the
  report message generation to produce abend 5C6-00F20058
  (CSQ2_QCP0_PUT1_ERROR).
  

Problem conclusion

• The expiry value used when putting the message to the DLQ or
  putting a report message has been corrected no longer use the
  invalid value, 0, in this scenario.
  100Y
  CSQ2MTOO
  CSQ2OTOM
  CSQ2QCP1
  

Temporary fix

Comments

APAR Information

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

  PI56425

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

  UI35696

Modules/Macros

• CSQ2MTOO CSQ2OTOM CSQ2QCP1
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R100 PSY UI35696

     UP16/04/12 P F604 ­

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.