IBM Support

SE60376: USING IBM I COMMITMENT CONTROL THE FIRST MESSAGE IS PROPERLY COMMITTED BUT MESSAGES FROM SUBSEQUENT COMMITS ARE NOT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using IBM i commitment control where multiple MQPUTs/MQGETs
    and COMMITs occur within the scope of one
    MQCONN/MQOPEN/MQCLOSE/MQDISC pairing, the message(s) from the
    first COMMIT are properly committed but the message(s) from
    subsequent COMMITs are not. This results in uncommitted messages
    on the queue.
    For example, the following sequence of events could result in
    uncommitted messages:
    MQCONN, MQOPEN, MQPUT message1, COMMIT, MQPUT message2, COMMIT,
    MQCLOSE, MQDISC
    In this example, message1 is properly committed but message2 is
    not. Whereas, this sequence results in both messages being
    committed properly:
    MQCONN, MQOPEN, MQPUT message1, MQPUT message2, COMMIT, MQCLOSE,
    MQDISC
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    WMQ users utilizing IBM i commitment control where multiple
    COMMITs are being executed within the scope of one MQCONN ->
    MQOPEN -> MQCLOSE -> MQDISC sequence.
    
    
    Platforms affected:
    IBM iSeries
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    WMQ code was not properly accounting for multiple COMMIT's in a
    single transactional boundary.
    

Problem conclusion

  • WMQ code has been modified to allow for proper execution of
    multiple COMMITs in a single transactional boundary.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v8.0       8.0.0.2
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    SE60376

  • Reported component name

    WMQ ISERIES V8.

  • Reported component ID

    5724H7254

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-07

  • Closed date

    2014-10-28

  • Last modified date

    2015-01-05

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

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

Modules/Macros

  • RCHMGR
    

Fix information

  • Fixed component name

    WMQ ISERIES V8.

  • Fixed component ID

    5724H7254

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
05 January 2015