PM85708: DEAD LETTER QUEUE HANDLER RECEIVES CSQU227E MQCC=2 MQRC=2195, SNAPDUMP IS CREATED AND SHOWS RC 00C510AF

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Running csqudqlh against a message in DLQ results in error:
  CSQU201I Processing queue DEAD.LETTER.QUEUE
  CSQU227E Unable to get message from dead-letter queue, MQCC=2
           MQRC=2195
  CSQU202I Dead-letter queue handler ending. Successful actions:
           0 retries, 0 forwards, 0 discards
  CSQU203I 1 messages remain on the dead-letter queue
  
  Snap dump is created and shows reason 00C510AF.
  Logrec also shows the abend too, but no dump is created.
  
  
  Problem occurs when an MQGET specifies MQMO_MATCH_MSG_TOKEN
  together with MQGMO_LOCK against a message on a shared queue.
  CSQIMGES invokes CSQEMGEK to retrieve the message, but it does
  not set CSQE_LOCK_MSG and hence CSQEMGEK does not invoke
  CSQETHDP for CSQE_CREATE_BRLOCK_TROP.
  CSQIMGES subsequently updates Browse_Locked with the message
  (with then results in BrowseLock being updated in the
  browse-cursor
  in the MHND by CSQMGET). This therefore results in the
  subsequent 5C6-00C510AF.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: 5C6-00C510AF when trying to get locked  *
  *                      messages by Msgtoken.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A 5C6-00C510AF, CSQE_MSG_BROWSE_LOCK_ERROR, issued by CSQEMULK
  occurred when using the dead-letter queue handler, CSQUDLQH.
  The abend occurs when a previous MQGET browse specifies
  MQMO_LOCK with MQGMO_MATCH_MSG_TOKEN against a message on a
  shared queue.
  CSQIMGES sets CSQE_LOCK_MSG but in subsequent processing
  replaces this with CSQE_GET_MSG_BY_TOKEN. This means that
  the browse lock TROP (Thread Related Operation) is not
  created which causes the subsequent abend.
  Additional Symptoms: 5C6-00C51133 CSQEMGEC MATCHOPTIONS
  

Problem conclusion

• CSQIMGES has been changed to OR the Options values with the
  msgtoken request, instead of replacing the previous Options.
  100Y
  CSQIMGES
  

Temporary fix

Comments

• ×**** PE14/05/13 FIX IN ERROR. SEE APAR PI10944  FOR DESCRIPTION
  

APAR Information

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

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

  UK93958

Modules/Macros

• CSQIMGES
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R100 PSY UK93958

     UP13/06/14 P F306

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.