WMQ5.3 Channels Stopped at QM Startup.

[roughagain]

I am interested to hear if anyone else has seen this situation as it happens to us now on many different servers.

It first started on MSCS clusters when we moved groups the queue manager started on the alternate node, but some channels went into the STOPPED state.
Now it has started to occur on single servers after they are rebooted.
Before the Queue Managers shutdown the channels are not stopped, but when the Queue Manager starts certain channels are regularly stopped so we have to manually start them. It happens to both Sender and Server Channels.

This has only started happening since we upgraded to WMQ5.3 CSD05 for Windows.
We have had a PMR open for some time now, but no solution yet and wonder whether we are really alone with the problem?
Would like to hear from anyone else who has experienced this.

Thanks,

 

[aixmurderer]

CSD 6 is available now, perhaps you should install that to see if it solves the problem.

The only similar occurance we have is if a sender channel is in long retry before the reboot, then it won't start after the reboot.

IBM Certified Confused - MQSeries
IBM Certified Flabbergasted - AIX 5 pSeries System Administration
MS Certified Windblows Rebooter