Fixes are available
APAR status
Closed as fixed if next.
Error description
After adding a remote queue manager to a WebSphere MQ (WMQ) Explorer set, a restart of the WMQ Explorer removes the newly added definition from that set.
Local fix
Remove any duplicate or hidden queue manager definitions, then rebuild the sets
Problem summary
The WMQ Explorer stores the information about which manager is in which set using a key which is constructed information including the name of the queue manager. If there are two or more instances of the the same queue in the WMQ Explorer and some are hidden, the next time the Explorer is restarted a particular instance of the queue can end up with the key from the other instance of the queue manager. The second instance may not have been part of the manual set, and so the queue manager no longer appears in that set.
Problem conclusion
Temporary fix
Comments
Closing as FIN (Fixed If Next Release). To resolve this problem duplicate instances of the same manager should be removed from the WMQ Explorer.
APAR Information
APAR number
IC67834
Reported component name
WMQ WINDOWS V7
Reported component ID
5724H7220
Reported release
700
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-04-13
Closed date
2010-05-25
Last modified date
2010-05-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
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