IBM Support

PI33509: WEBSPHERE MQ V701, MQ Z/OS SHOULD NOT BE BACKING-OUT THE TRANSACTION WHEN THE PROTOCOL VIOLATION OCCURS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • The backout is occurring as an XA CLOSE is being issued while
    the associated transaction is active, which is a protocol
    violation. However, the associated transaction is in PREPARED
    state, so it is incorrect for it to be backed-out. This
    problem has been fixed in the base code of V710 (defect
    139570).
    
    
    Additional Symptom(s) Search Keyword(s): XA CLOSE transaction
    backout
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When doing the following XA sequence,   *
    *                      any recoverable work is rolled back by  *
    *                      MQ without waiting for a decision from  *
    *                      transaction coordinator:                *
    *                      xa_open                                 *
    *                      xa_start                                *
    *                        -> recoverable work                   *
    *                      xa_end                                  *
    *                      xa_prepare                              *
    *                      xa_close                                *
    *                                                              *
    *                      Note that this sequence constitutes a   *
    *                      protocol error.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    CSQMXARH rolls back the transaction when the XA_CLOSE request
    is issued without checking if the current state is PREPARED or
    not. If it is in the PREPARED state, the unit of work should be
    left in-doubt.
    

Problem conclusion

Temporary fix

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

Comments

  • The code was changed to correctly handle this protocol error.
    

APAR Information

  • APAR number

    PI33509

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-27

  • Closed date

    2015-02-24

  • Last modified date

    2015-05-04

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

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

    UI25401

Modules/Macros

  • CSQMCPRH CSQMXARH
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UI25401

       UP15/04/30 P F504 Ž

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 May 2015