PI12484: IN SYNCPOINT WORK DONE ON AN XA CONNECTION BUT OUTSIDE OF AN XA TRANSACTION GETS INCLUDED IN A LATER XA TRANSACTION.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• If an XA client connects to MQ z/OS and performs an in-syncpoint
  MQPUT or MQGET while there is no active XA transaction, the
  request is allowed to complete successfully but the work can
  become associated with a subsequent XA transaction on the same
  connection.
  This can result in the MQPUT or MQGET being unexpectedly
  committed or backed out depending on the result of the
  subsequent transaction.
  

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: If an XA enabled client performs an     *
  *                      in-syncpoint MQPUT or MQGET request     *
  *                      while no XA transaction is active,      *
  *                      the work done will be committed or      *
  *                      backed out depending on the result      *
  *                      of the next transaction on the same     *
  *                      connection.                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An MQ client application connects to an MQ for z/OS queue
  manager and issues an XA_OPEN call to allow XA coordination of
  transactional work on the connection.
  The client issues an MQPUT call with MQPMO_SYNCPOINT or an MQGET
  call with MQGMO_SYNCPOINT or MQGMO_SYNCPOINT_IF_PERSISTENT
  without the transaction manager having first issued an XA_START.
  In these circumstances, the MQPUT or MQGET request should fail
  with reason code 2072 (MQRC_SYNCPOINT_NOT_AVAILABLE), but the
  z/OS queue manager incorrectly allows it to complete without
  error.
  If a subsequent XA_START call is made on the same connection,
  the work performed by the MQPUT or MQGET becomes part of the
  XA transaction and will be committed or backed out depending
  on the result of that transaction.
  

Problem conclusion

• MQ for z/OS will be changed to reject the MQPUT or MQGET request
  with reason code 2072 (MQRC_SYNCPOINT_NOT_AVAILABLE).
  010Y
  100Y
  CSQMCPRH
  CSQMGETV
  CSQMPUTV
  CSQMTPUV
  CSQMXARH
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UI16933 UI16934

Modules/Macros

• CSQMCPRH CSQMGETV CSQMPUTV CSQMTPUV CSQMXARH
  

Fix information

• Fixed component name

  WMQ Z/OS V7

• Fixed component ID

  5655R3600

Applicable component levels

• R010 PSY UI16933

     UP14/04/23 P F404 ¢

• R100 PSY UI16934

     UP14/04/23 P F404 ¢

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.