Author |
Message
|
Nizam |
Posted: Thu Oct 29, 2009 11:36 am Post subject: export MQ_CHANNEL_SUPPRESS_MSGS=9209 |
|
|
Disciple
Joined: 10 Feb 2004 Posts: 160
|
WebSphere MQ 6.0.2.3, Solaris 10
I plan to use
export MQ_CHANNEL_SUPPRESS_MSGS=9209
to suppress 9209 error messages that are filling up in the error logs.
Do I have to restart queue managers/server after running this command.
I looked up documentation but could find an answer.
Thank you,
nizam |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Oct 29, 2009 12:33 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
|
Back to top |
|
 |
Nizam |
Posted: Thu Oct 29, 2009 1:08 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004 Posts: 160
|
Thanks for your reply. I have seen that link before.
All channels seem to be running fine. Since we are not able to identify the source that is causing the 9209 error messages, we have decided to suppress the 9209 error messages.
I was wondering if queue manager/server need to be restared after doing export MQ_CHANNEL_SUPPRESS_MSGS=9209 |
|
Back to top |
|
 |
gbaddeley |
Posted: Thu Oct 29, 2009 3:46 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
Nizam wrote: |
I was wondering if queue manager/server need to be restared after doing export MQ_CHANNEL_SUPPRESS_MSGS=9209 |
I would say yes. Assuming you put this command in the logon profile script for the mqm userid, it would take effect next time the qmgr processes were started from a new mqm logon session that had this setting in its environment variables. _________________ Glenn |
|
Back to top |
|
 |
exerk |
Posted: Thu Oct 29, 2009 4:39 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
You might want to consider...
Code: |
QMErrorLog:
SuppressMessage = 9209 |
...in the qm.ini file. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
imsiva_k |
Posted: Mon Oct 11, 2010 3:21 am Post subject: Performace |
|
|
Apprentice
Joined: 02 Dec 2008 Posts: 25
|
Hello All,
Please help me that will it cause any performance degradation if we implement MQ error message suppressing ?
Many thanks in advance |
|
Back to top |
|
 |
exerk |
Posted: Mon Oct 11, 2010 4:15 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Firstly, please do not re-open year-old threads, start a new one...
Why do you think that a performance degradation would occur if you implement suppression? What is your reasoning/concern/issue? It could be argued that anything that causes a large number of messages to be written to the log, that cause the logs to roll frequently, is something to be investigated and fixed - it is more likely that what is causing the error messages to be written too frequently is going to be a cause of performance degradation than the printing of such information. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Oct 11, 2010 5:24 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Suppressing the error message does not suppress the underlying problem. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
imsiva_k |
Posted: Mon Oct 11, 2010 9:34 pm Post subject: Suppressing error message |
|
|
Apprentice
Joined: 02 Dec 2008 Posts: 25
|
Hi All,
I am using MQ version 5.3 with CSD 13. I am trying to suppress some error message. However the problem here is I cant use the qm.ini file to implement this. I need to export the variable to suppress the error message coz version 5.3. One concern which I am worried about is , for example if I have two queue manager in a machine and I would like to suppress the error message in only one queue manager by exporting the variable, how can i implement this ?
Thanks in advance. |
|
Back to top |
|
 |
exerk |
Posted: Mon Oct 11, 2010 10:36 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
1. Upgrade because you are way out of support;
2. Fix the underlying problem that is causing your issue, as has been suggested;
3. Upgrade because you are way out of support.
If that variable is global then all queue managers will pick it up, so you cannot separate. Follow the advice of 1, 2 and 3 above... _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
imsiva_k |
Posted: Mon Oct 11, 2010 10:57 pm Post subject: |
|
|
Apprentice
Joined: 02 Dec 2008 Posts: 25
|
Thanks so very much for the reply.
However the problem is we have lot of dependency over version 5.3. We use ENCINA application to interact with MQ version 5.3. I am afraid that we need to use the same version unless and until we decommission encina cos the encina application is complied with v 5.3 libraries. Please correct me if I am wrong.
Regarding the error messages, I tried suppressing the error message by exporting the below variable.
export MQ_CHANNEL_SUPPRESS_MSGS=9999,9002. Re-logged in and restarted the QM. However still am getting the logs for 9999 and 9002 events.
Could you please help me in this regard ? |
|
Back to top |
|
 |
exerk |
Posted: Mon Oct 11, 2010 11:36 pm Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
And when you logged back in did you check that the variable was set before restarting the queue manager? Maybe a better place to put that variable declaration would be in the .profile for mqm? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
imsiva_k |
Posted: Mon Oct 11, 2010 11:48 pm Post subject: |
|
|
Apprentice
Joined: 02 Dec 2008 Posts: 25
|
Exactly. I added in similar way in .profile file under mqm login. Even then it is not working. |
|
Back to top |
|
 |
exerk |
Posted: Tue Oct 12, 2010 2:22 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
And as it's out of support, you can't open a PMR...
The only recourse you now have is to fix the underlying problem. If it's only happening on one of your two queue managers you at least have narrowed the field a bit. Please let us know how you get on. _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 12, 2010 2:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
There's no guarantee that MQ v5.3 has support for an environment variable discussed in a thread for v6.
I know there are some qm.ini stanzas for suppressing error messages, but again probably not in v5.3. |
|
Back to top |
|
 |
|