PM70204: WEBSPHERE MQ V710, RESET QSTATS MSGSIN/MSGSOUT IS INCORRECT WHERE MESSAGES ARE PROCESSED VIA 'FAST PUT'

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Error Description￘
  Using RESET QSTATS command to get queue statistics, But it
  seems that the values of MSGSIN and MSGSOUT
  is not correct reported (in customers case always 0)
   when the following is used
  - putting non persistant messages
  - WMQ V7.1
  - putting to a waiting getter
  
  Here is the output of the original "reset qstats" command:
  
  1.) After  putting 1 message to the queue, no waiting getter:
  reset qstats(TEST.QUEUE.HWV.REQUEST)
  CSQN205I   COUNT=       3, RETURN=00000000, REASON=00000000
  CSQM451I MQBT QSTATS(TEST.QUEUE.HWV.REQUEST) QSGDISP(SHARED)
  RESETINT(85)
  HIQDEPTH(1) MSGSIN(1) MSGSOUT(0)
  CSQ9022I MQBT CSQMDRTS ' RESET QSTATS' NORMAL COMPLETION
  
  2.) After getting message from same queue:
  reset qstats(TEST.QUEUE.HWV.REQUEST)
  CSQN205I   COUNT=       3, RETURN=00000000, REASON=00000000
  CSQM451I MQBT QSTATS(TEST.QUEUE.HWV.REQUEST) QSGDISP(SHARED)
  RESETINT(267)
  HIQDEPTH(1) MSGSIN(0) MSGSOUT(1)
  CSQ9022I MQBT CSQMDRTS ' RESET QSTATS' NORMAL COMPLETION
  
  3.) After putting 1 message to the same queue while a waiting
  getter is
  consuming it:
  reset qstats(TEST.QUEUE.HWV.REQUEST)
  CSQN205I   COUNT=       3, RETURN=00000000, REASON=00000000
  CSQM451I MQBT QSTATS(TEST.QUEUE.HWV.REQUEST) QSGDISP(SHARED)
  RESETINT(38)
  HIQDEPTH(0) MSGSIN(0) MSGSOUT(0)
  CSQ9022I MQBT CSQMDRTS ' RESET QSTATS' NORMAL COMPLETION
  
  For number 3.) have expected MSGSIN(1) MSGSOUT(1) but
  got MSGSIN(0) MSGSOUT(0)
  
  Looks the current behaviour of RESET QSTATS MSGSIN/MSGSOUT is
  incorrect in this situation where messages are processed via
  'fast put'
  

Local fix

• Local Fix￘
  none
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 1 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: RESET QSTATS shows wrong values for a   *
  *                      queue with non-persistent messages.     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a customer issues a RESET QSTATS for a queue the MSGSIN and
  MSGSOUT values do not reflect the actual number of Puts and Gets
  that have occurred since the last RESET.
  This happens when the queue has non-persistent messages, and it
  is being processed by a waiting getter which is not within a
  syncpoint. When these criteria are met, the fast put code is
  invoked, and this code does not currently update the statistics
  used by the RESET QSTATS command.
  

Problem conclusion

• CSQM1PFW has been updated to update lIAMsgDeqCount and
  lIAMsgEnqCount in the MPDO.
  CSQMPUTI has been updated to call CSQM1PFW with the address
  of the IVSA.
  100Y
  CSQMPUTI
  CSQM1PFW
  

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:

  UK90338 PM87197

Modules/Macros

•    CSQMPUTI CSQM1PFW
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R100 PSY UK90338

     UP13/02/05 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.