The MQ product reports various conditions and changes through the MQ diagnostic messages. These could either be reported directly to the admin’s console or in various error log files, such as AMQERR01.LOG.

An example message might be

AMQ8118: IBM MQ queue manager does not exist

The MQ product family can now append a severity character to the message id. The above would be come

AMQ8118E: IBM MQ queue manager does not exist

the E following AMQ811 denotes it an error message.

Severity Characters

Each MQ message has a severity level

I : Information
W : Warning
E : Error
S : Severe Error
T : System error or termination.

to indicate the immediate attention it requires and up to now this severity level was not included in the message.

MQ 9.0.3

In MQ continuous delivery release 9.0.3, a new opt-in feature was included to append a severity character to these messages. To enable this feature, create the environment variable AMQ_DIAGNOSTIC_MSG_SEVERITY with a value of 1 before using a MQ command i.e. starting or restarting a queue manager with strmqm.

MQ 9.0.4

In MQ continuous delivery release 9.0.4 this was reversed so the severity character was included by default. For those who have scripts which are dependent on the old message format, it can be disabled by creating environment variable AMQ_DIAGNOSTIC_MSG_SEVERITY with a value of 0 before using an MQ command.

Perl RegEx Parsers

For those monitoring these error logs and using a regular expression to match the message id value, append the sequence [IWEST]? to the end of your pattern match. This will cover for all severity characters(9.0.4) including no character present (9.0.3).

Useful Knowledge Center links

IBM MQ Message https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.ref.doc/q050260_.htm

Error Logs https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.tro.doc/q039560_.htm

Leave a Reply