Fixes are available
APAR status
Closed as program error.
Error description
Client applications using the MQ V7 client to communicate with an MQ V7 server, that use a non zero SHARECNV value, and that repeatedly use MQGMO_BROWSE_FIRST may not be delivered the expected sequence of messages. MQ V7 applications that use both MQGMO_BROWSE_FIRST and MQGMO_BROWSE_NEXT on the same MQCB call may not be delivered the expected sequence of messages.
Local fix
Apply fix or optional workaround: the user may enable BROWSE_WITH_MARK which will suppress the problem.
Problem summary
**************************************************************** USERS AFFECTED: This problem affects applications that specify both MQGMO_BROWSE_FIRST and MQGMO_BROWSE_NEXT in the MQGMO passed to on MQCB call. One such application is the MQ V7 client proxy (amqrmppa/amqcrsta) which uses this function in implementing an MQGET with MQGMO_BROWSE_FIRST from an MQ V7 client that uses a non zero SHARECNV value. Platforms affected: All Distributed (iSeries, all Unix and Windows) **************************************************************** PROBLEM SUMMARY: This problem affects programs that specify both MQGMO_BROWSE_FIRST and MQGMO_BROWSE_NEXT in the MQGMO passed to an MQCB call. The specification of this combination of options states "The browse cursor is reset to the start of the queue and the consumer is then given each message on the queue until the end of the queue is reached". The intent of this specification is to not require the application to issue an MQCTL STOP/START sequence to change the browse options from MQGMO_BROWSE_FIRST to MQGMO_BROWSE_NEXT after the first message has been consumed. In some circumstances the implementation of this behaviour was incorrectly resetting the MQGMO_BROWSE_FIRST bit before the browse cursor had been repositioned, leading to an incorrect sequence of messages being returned to the browse.
Problem conclusion
The code is changed such that the cursor position is always established before the transition of an MQCB that specified both MQGMO_BROWSE_FIRST and MQGMO_BROWSE next, from MQGMO_BROWSE_FIRST behaviour to MQGMO_BROWSE_NEXT behaviour occurs. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: v7.0 Platform Fix Pack 7.0.1.1 -------- -------------------- Windows U200310 AIX U827232 HP-UX (PA-RISC) U826485 HP-UX (Itanium) U826884 Solaris (SPARC) U827125 Solaris (x86-64) U827374 iSeries tbc_p700_0_1_1 Linux (x86) U826321 Linux (x86-64) U827231 Linux (zSeries) U827105 Linux (Power) U826779 v7.0 Currently any fixes planned for v7.0 will be fixed in 7.0.1.* and not in 7.0.0.* 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
IC61336
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-06-02
Closed date
2009-07-31
Last modified date
2009-11-24
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ WINDOWS V7
Fixed component ID
5724H7220
Applicable component levels
R700 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 March 2023