A fix is available
APAR status
Closed as program error.
Error description
Stopped the CPU. Found the Cluster Sender Channel was stopped The event AMQ9604 Cluster Sender Channel stopped unexpectedly was reported. When the qmgr was restarted the channel remained in an inactive state. When messages were put via the channel the messages remained in the SYSTEM.CLUSTER.REPOSITORY.QUEUE The channel had to be manually restarted.
Local fix
Problem summary
If a CLUSSDR or SDR channel is running in an MCA that is in the same CPU as the Primary Channel Server, and that channel has been running for at least 5 minutes, and that CPU crashes, the channel will not automatically restart. This is a consequence of the Takeover logic in the channel server unsetting the InUse flag for the channel, because the RETRY flag has not been set. This in turn prevents the Channel Retry logic from attempting to restart the channel.
Problem conclusion
If the Channel Server is performing a Takeover, the channel status should be updated to RETRY and the InUse flag should be left as is, therby causing the channel retry logic to be executed.
Temporary fix
Start the affected channel manually
Comments
APAR Information
APAR number
IC89751
Reported component name
WEBS MQ NSS ITA
Reported component ID
5724A3902
Reported release
531
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-01-22
Closed date
2013-01-22
Last modified date
2013-01-22
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
WEBS MQ NSS ITA
Fixed component ID
5724A3902
Applicable component levels
[{"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":"5.3.1"}]
Document Information
Modified date:
17 November 2020