MQ

 View Only

IBM MQ Little Gem #11: ExcludeMessage

By Morag Hughson posted Tue April 26, 2016 03:06 AM

  
This is part of a series of small blog posts which will cover some of the smaller, perhaps less likely to be noticed, features of IBM MQ. Read other posts in this series.

Inspect Error Log.jpgDo you ever feel like you can't see the wood for the trees in your queue manager error log? Got so many messages of a minor issue, say a network error, that you didn't notice a more major one?

At times like those, it may be worth excluding some error messages from your error log so you can see the rest. You should of course be careful with this that you don't exclude things long term that may be important, but as a temporary measure it may be very useful.

Both the distributed and z/OS products have this capability though a similar keyword.

Excluding error messages on distributed

On distributed, you use the ExcludeMessage keyword, and the error message numbers you wish to exclude, in the QM.INI file. You are not allowed to exclude any message, but a selection of those determined as appropriate to exclude, from those listed in Knowledge Center. Messages are specified without the AMQ prefix. You can also configure the distributed queue manager to only write certain messages once per time interval. This can be useful to quieten down your error log if you get a flood of messages due to a particular issue and is especially handy for network related problems. You don't need 100 different channels all reporting the same thing to know that you've had an issue, one would do!

Here is an example:

QMErrorLog:
   ExcludeMessage=9001,9002
   SuppressMessage=9202,9208,9209
   SuppressInterval=30

Excluding error messages on z/OS

On z/OS, from V8, you can use the EXCLMSG keyword on the SET SYSTEM command (or via the CSQ6SYSP macro to add them to the queue manager's ZPARM parameter module used at startup). You can choose to exclude any message issued by the MSTR or CHIN address spaces once they have completed start-up. You can't exclude messages issued elsewhere, for example messages from CSQUTIL. Messages are specified without the CSQ prefix and without the action code suffix.

Here is an example:

SET SYSTEM EXCLMSG(X500,X501,X511,X512)

Client channel start/end messages

A common requirement might be to exclude channel start and channel normal end messages (both above examples show messages 9001 and X501 - channel ended normally - and 9002 and X500 - channel started). Additionally on z/OS it is very common to want to exclude the SVRCONN started and ended messages. In fact these are permanently excluded on the distributed queue managers and cannot be reinstated. On z/OS, to allow exclusion for these messages without impacting the MCA channel messages, these were given different message numbers in MQ V8 so you can exclude X511 and X512 separately.

 

So if your queue manager error log is full of things you don't want to scroll past, have a look at what might be useful to exclude or suppress.


Morag Hughson is an MQ expert. She spent 18 years in the MQ Devt organisation before taking on her current job writing MQ Technical education courses with MQGem. She also blogs for MQGem. You can connect with her here on IMWUC or on Twitter and LinkedIn.


#Little-Gem
#IBMMQ
#IBMChampion

0 comments
23 views

Permalink