A fix is available
APAR status
Closed as program error.
Error description
The WebSphere MQ v7.0.1 Explorer is displaying 'Unknown' status in the Uncommitted messages column on the queue status panel. The WebSphere MQ Explorer is being used to remotely administer a Solaris queue manager. When the queue is browsed no messages are displayed. The WebSphere MQ Explorer is showing a current queue depth of 4, and this is also the value seen from the runmqsc command line output when issuing the command: . dis qs(queuename) curdepth uncom
Local fix
Upgrade to WMQ v7.1 Explorer
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the WebSphere MQ V7.0.1 Explorer who are checking the status of queues on WebSphere MQ V7.0.1.4 queue managers (and later) on distributed platforms. Platforms affected: Linux (x86),Linux (x86-64),Windows **************************************************************** PROBLEM SUMMARY: When using the WebSphere MQ Explorer to display the status of a queue in the Queue Status panel, WebSphere MQ Explorer queries the queue manager that the queue resides upon. WebSphere MQ Explorer uses the value of the 'UNCOM' attribute that is returned by the queue manager to determine if there are uncommitted messages on the queue. WebSphere MQ Explorer then uses this information to populate the "Uncommitted messages" field on the Queue Status panel. WebSphere MQ V7.0.1.3 queue managers (and earlier) on distributed platforms, and all WebSphere MQ for z/OS queue managers, always return one of two possible values for this 'UNCOM' attribute: . 0 - there are no uncommitted messages on the queue. . 1 - there is at least one uncommitted message on the queue. WebSphere MQ V7.0.1.4 queue managers (and later) on distributed platforms return the 'UNCOM' attribute with a value that represents the actual number of uncommitted messages on the queue. This new behaviour was introduced in APAR IZ76189, first shipped with WebSphere MQ V7.0.1.4: http://www.ibm.com/support/docview.wss?uid=swg1IZ76189 The WebSphere MQ Explorer expected that all queue managers would return either 0 or 1 for the value of the 'UNCOM' attribute, and mapped them to the strings "No" and "Yes" respectively when filling in the "Uncommitted messages" field on the Queue Status panel. When the WebSphere MQ Explorer was connected to a WebSphere MQ V7.0.1.4 queue manager (or later) that had more than 1 uncommitted message on a queue, the value of the 'UNCOM' attribute returned by the queue manager would be outside of the range of values that the WebSphere MQ Explorer was expecting. This resulted in the WebSphere MQ Explorer displaying the text: [Unknown] in the "Uncommitted messages" field on the Queue Status panel.
Problem conclusion
The WebSphere MQ Explorer has been updated to display the following information in the "Uncommitted messages" field on the Queue Status panel: No: -------------------- If there are no uncommitted messages on the queue. Yes: --------------------- If the queue being monitored by MQ Explorer is either: 1) A queue on a WebSphere MQ for z/OS queue manager or a queue on a WebSphere MQ V7.0.1.3 (or earlier) queue manager on a distributed platform, and the queue contains at least one uncommitted message. 2) A queue on a WebSphere MQ V7.0.1.4 (or later) queue manager on a distributed platform that contains exactly one uncommitted message. A numerical value: ------------------ If the queue being monitored is running on a WebSphere MQ V7.0.1.4 (or later) queue manager on a distributed platform, and the queue contains more than one uncommitted message and less than 65536 uncommitted messages. [Unknown] ------------------ If the queue being monitored is running on a WebSphere MQ V7.0.1.4 (or later) queue manager on a distributed platform, and the queue contains 65536 or more uncommitted messages. As a result of the code change associated with this APAR, the WebSphere MQ V7.0.1 Explorer behaves in the same way as the WebSphere MQ V7.1 Explorer when populating the "Uncommitted messages" field on the Queue Status panel. | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0004 | | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0004 | | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0004 | | MDVPARTL 7.0.1-WS-MQ-Windows-FP0004 | | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0005 | | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0005 | | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0005 | | MDVPARTL 7.0.1-WS-MQ-Windows-FP0005 | | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0006 | | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0006 | | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0006 | | MDVPARTL 7.0.1-WS-MQ-Windows-FP0006 | | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0007 | | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0007 | | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0007 | | MDVPARTL 7.0.1-WS-MQ-Windows-FP0007 | | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0008 | | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0008 | | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0008 | | MDVPARTL 7.0.1-WS-MQ-Windows-FP0008 | | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0009 | | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0009 | | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0009 | | MDVPARTL 7.0.1-WS-MQ-Windows-FP0009 | --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.1.10 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
IC83324
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
701
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-05-10
Closed date
2012-06-26
Last modified date
2013-11-28
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
R701 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]
Document Information
Modified date:
20 September 2021