PI27552: WEBSPHERE MQ, UNCOMMITTED MQGET IS NOT BEING BACKED-OUT FOLLOWING THE RESTART OF RRS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In this case the unit of work is indoubt. the unit of work
  is associated with an MQ private context and a global RRS
  transaction. The queue-manager has been invoked by RRS for
  prepare processing, so the queue-manager has flagged the unit
  of work as indoubt. However, RRS has been cancelled before it
  has logged the end of the prepare phase. When RRS was
  restarted, it did not return the UR for the global transaction
  (as the UR was not logged by RRS) on any of the the ATRIRNI
  calls issued by CSQ3RRSR. The queue-manager resync processing
  in CSQ3RRSR then detected that this context needed to be ended
  (and hence the transaction backed-out) and therefore scheduled
  deferred end-context processing. However, when the deferred
  end-context was processed by CSQMCTXE it detected that there
  was a global RRS transaction and did not perform end-context
  processing, the assumption being that RRS will subsequently
  drive the queue-manager for commit or abort, after which the
  context could be ended. However, as RRS was restarted when the
  transaction was inflight (from RRS's perspective)this was never
  going to happen, so the MQGET and MQPUT remained uncommitted.
  
  
  
  Additional Symptom(s) Search Keyword(s): RRS UNCOM indoubt
  inflight
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
  *                 Release 0 Modification 1 and Release 1       *
  *                 Modification 0.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: RRS going away during a commit that     *
  *                      uses a MQ private context, such as      *
  *                      WebSphere Application Server, may leave *
  *                      uncommitted units of work after RRS is  *
  *                      restarted. These units of work will be  *
  *                      resolved when the queue manager is      *
  *                      restarted.                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During a commit by an application that uses a MQ private context
  such as WebSphere Application Server, if RRS goes away during
  the processing, the associated unit of work can be inflight from
  RRS's perspective but indoubt from MQ's perspective. When RRS
  becomes available again, after RRS resync processing the UOW
  remains indoubt. This UOW will only be resolved once the queue
  manager is restarted.
  

Problem conclusion

• RRS resync processing has been updated to resolve the indoubt
  UOW correctly in the case it is inflight from RRS's perspective.
  010Y
  100Y
  CSQ3RRSR
  

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:

  PI28644 UI23190 UI23191

Modules/Macros

• CSQ3RRSR
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UI23190

     UP14/12/04 P F412

• R100 PSY UI23191

     UP14/12/04 P F412

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.