| Author |
Message
|
| PeterPotkay |
 Posted: Wed May 15, 2002 8:11 am Post subject: Do you have to restart a QM to pick up attribute changes? |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
oS/400 Queue Manager version 5.1
If I change the TriggerInterval parameter, do I need to restart the QM to pick up the changes? Where is this answer documented? I couldn't find anyhting one way ot the other.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Wed May 15, 2002 8:15 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Stopping and re-starting the channel should get the changes into effect.
Not quite sure where to search for in the manuals for this. But i guess should be somewhere deep in the Intercommunication guide.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed May 15, 2002 8:19 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Stopping and re-starting the channel should get the changes into effect.
You meant the QM, right?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed May 15, 2002 8:24 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
No.
stop chl(<chl>)
start chl(<chl>)
All channel defs are stored in cache until the channel is active. Hence any changes made to it's attributes dont take effect until you stop and restart the channel itself. This way the new attributes are stored into the cache and become effective.
Except for Clustering, no other object needs a QM restart.
Hope this helps.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed May 15, 2002 8:32 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I just want to make sure we are on the same page. TriggerInterval has nothing to do with channels directly, which is why your original reply confused me.
From your 2nd reply, I infer that changing the triggerinterval paramaeter or default transmit queue parameter for instance, will not need a QM restart before the Qm starts recognizing these changes, while a channel parameter change requires a channel restart, corect?
Thanks.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqonnet |
| Posted: Wed May 15, 2002 8:39 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Good spot Pete.
I have been doing so much of channels that everything seems channels to me. :D
But in any case the answer was not completely off topic and holds good for this problem as well.
You dont need to restart your QM for changes made to trigint, as far as i know. I remember doing this a long while ago, but pretty much sure that a QM restart is not required.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
|
|
