A fix is available
APAR status
Closed as program error.
Error description
Customer complained the status of cluster sender channel(auto-defined) issuing by "dis clusqmgr" is incorrect and inconsistent with that issuing by "dis chs" on z/OS if cluster receiver channel is defined with multiple connection names on other side. If cluster receiver channel is defined with single connection name, the status of "dis clusqmgr" on z/OS is expected and is consistent with that of by issuing "dis chs". IBM change team recreated issue that the problem occurs as rriUPDATE_CACHE_CHL_STATE does not update the state of the channel when rriSO_RETRYABLE_SESSION is set (i.e. multiple addresses in the CONNAME). Note: the problem does not occur if the last connection-name in the separated list is used to connect to the partner.
Local fix
N/A.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Command DISPLAY CLUSQMGR(*) shows the * * incorrect STATUS when the CLUSSDR * * channel to the queue manager has * * been defined with attribute CONNAME * * with multiple connection names or * * network addresses. * **************************************************************** * RECOMMENDATION: * **************************************************************** The command DISPLAY CLUSQMGR(*) should show an STATUS that matches the STATUS of the CLUSSDR channel to each queue manager. In the case that the channel has multiple connection names or addresses the update of the cluster queue manager status is skipped when the channel status changes.
Problem conclusion
Function rriSendData (CSQXRMTR) now updates the cluster queue status when the CLUSSDR channel status has changed. 100Y CSQXRMTR
Temporary fix
Comments
APAR Information
APAR number
PI82542
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-06-04
Closed date
2017-08-31
Last modified date
2017-10-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
CSQXRMTR
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI49979
UP17/09/28 P F709
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.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 October 2017