PM81522: DELAY IN RESETTING THE BROWSE-MARKS AND CAN CAUSE A DELAY IN GETTING THE MESSAGE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The customer is running WebSphere MQ V701 and has a QSG defined
  with two QMGRs with WAS V7.0.0.23. WebSphere Application Server
  is using a MDB Listener to get the messages and sometimes they
  receive a MQRC 2033 when there is a message on the queue.
  The change team has continued to review the docs for the delay
  in resetting the browse-marks and they can now see the cause of
  the problem. In the case of the message which was got at
  2:29:57.002 GMT (returned to WAS at 2:29:56.984 GMT in the
  GTF trace), this message should have been expired by CSQEMTIN
  when it on CSQ1MSTR at 2:30:06.832 GMT. CSQEMTIN tried to update
  the MQSH with the new co-op mark (currently 01, so new co-op
  mark should have been 02 and messages with co-op mark 03, such
  as the message referred to above, been expired). However, the
  update of the MQSH needed to be retried, which resulted in the
  new co-up being set to 03 and messages with co-op mark 01 were
  expired (although there were none of these). This meant
  that the message got at 2:29:57.002 GMT did not get expired
  until CSQEMTIN ran several intervals later, at 2:30:16.878 GMT.
  The same problems is the reason for the delay in resetting the
  browse-mark for the message got at 2:30:17.121 GMT.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ Version 7          *
  *                 Release 0 Modification 1 and                 *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Messages mark-browsed by an application *
  *                      ( such as WAS MDBs ) using browse with  *
  *                      mark for a shared queue, may take       *
  *                      longer than expected to be unmarked.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The process that unmarks messages is missing opportunities to
  expire marks when the update of the shared queue state has to
  be retried in the coupling facility.
  

Problem conclusion

• The message unmark process has been changed to not skip
  expiring marks during the retry of updating shared queue state.
  010Y
  100Y
  CSQEMTIN
  

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:

  UK91764 UK91765

Modules/Macros

• CSQEMTIN
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UK91764

     UP13/03/01 P F302

• R100 PSY UK91765

     UP13/03/01 P F302

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.