MQSeries.net :: View topic

PeterPotkay

Windows 2000.
MQ 5.3.0.8

Server1 has 2 QMs, QM1 and QM2.

QM1 is a plain QM.
QM2 is under the control of Microsoft Cluster Services.

If I change a QM property thru MQ Services, the change sticks with the QM the next time I start it no matter when I changed it originally. For instance, I change the Max Channels to 1234. The next time the QM starts, Max Channels will be 1234, whether I changed it when the QM was running, or when the QM was stopped.

BUT,
If the QM is run by MQSC, the change only takes if the QM is online when I make the change!

QM is online and has Max Channels set to 1000.
Bring QM offline. Change Max Channels to 1500. Apply. OK. Bring QM online. Max Channel is back to 1000!

QM is online and has Max Channels set to 1000.
Change Max Channels to 2000(while QM is online). Apply. OK. Bring QM offline. Bring QM online. Max Channel is correctly at 2000.

QM is online and has Max Channels set to 1000.
Change Max Channels to 3000(while QM is online). Apply. OK. Bring QM offline. Change Max Channels to 4000 (while QM is offline) Bring QM online. Max Channel is at 3000!

Its like a QM under MSCS has all its properties cached at offline time, and nothing takes while you change it when it is offline. I used the Max Channels as an example, but it effects other parameters to. We went crazy with an API exit and this behaviour. (I swear I deleted the Exit! No you didn't! Yes I did! No you didn't! Look, its still there. What the......?!?!)

Is this behaviour documented anywhere?
_________________
Peter Potkay
Keep Calm and MQ On