Diagnostic message service stanzas
The diagnostic message service options available enable customization of the IBM MQ diagnostics logging, so that log output can be directed to different log end points from different components of IBM MQ.
You enable additional diagnostic message services, using a stanza with one of the following names:- DiagnosticSystemMessages
Defines the services used when a diagnostic message is generated that goes to the system error log. Valid in the mqs.ini or mqclient.ini files.
Client applications use a DiagnosticSystemMessages stanza in the mqclient.ini file and in mqs.ini, the DiagnosticSystemMessages stanza controls messages for a server application that does not have a queue manager context.
It is possible for you to configure a queue manager and applications that additionally write all messages to the syslog service.
- DiagnosticMessages
Defines the services used when a diagnostic message is generated that goes to the queue manager error log. Valid only in the qm.ini file.
- DiagnosticMessagesTemplate
A stanza that is copied from the mqs.ini file to DiagnosticMessages in the qm.ini file when a queue manager is created.
To display diagnostic messages, use the mqrc command.
Attributes of the stanzas
Attention: Service, and a name of a stanza are mandatory.
- name=<stanzaname>
- Name of a stanza. The value must be unique in an ini file.
- Service= type of service
-
This attribute defines a service, where the name of the service is not case sensitive, that is being enabled by this stanza.
For example, to enable syslog as an additional service, enter the following:Service=syslog
See Diagnostic message services and their specific attributes that are available for use with the diagnostic message service stanzas.
We can add the following optional attributes to the stanzas:
- ExcludeMessage= msgIds
- Specifies messages that are not to be written to the queue manager error log. If the IBM MQ system is heavily used, with many channels stopping and
starting, a large number of information messages are sent to the z/OS console and hardcopy log. The IBM MQ - IMS
bridge and buffer manager might also produce a large number of information messages, so excluding
messages prevents you from receiving a large number of messages if you require it.
msgIds contain a comma-separated list of message id's from the following:
- 5211 - Maximum property name length exceeded.
- 5973 - Distributed publish/subscribe subscription inhibited
- 5974 - Distributed publish/subscribe publication inhibited
- 6254 - The system could not dynamically load shared library
- 7234 - Number of messages loaded
- 8245 - Entity has insufficient authority to display object
- 9001 - Channel program ended normally
- 9002 - Channel program started
- 9202 - Remote host not available
- 9208 - Error on receive from host
- 9209 - Connection closed
- 9228 - Cannot start channel responder
- 9489 - SVRCONN max instances limit exceeded
- 9490 - SVRCONN max instances per client limit exceeded
- 9508 - Cannot connect to queue manager
- 9524 - Remote queue manager unavailable
- 9528 - User requested closure of channel
- 9545 - Disconnect interval expired
- 9558 - Remote Channel is not available
- 9637 - Channel is lacking a certificate
- 9776 - Channel was blocked by user ID
- 9777 - Channel was blocked by NOACCESS map
- 9782 - Connection was blocked by address
- 9999 - Channel program ended abnormally
- SuppressMessage= msgIds
- Specifies messages that are written to the queue manager error log once only in a specified time
interval. If the IBM MQ system is heavily used, with
many channels stopping and starting, a large number of information messages are sent to the z/OS console and hardcopy log. The IBM MQ - IMS
bridge and buffer manager might also produce a large number of information messages, so suppressing
messages prevents you from receiving a number of repeating messages if you require it. The time
interval is specified by SuppressInterval. msgIds contain a
comma-separated list of message identifiers from the following:
- 5211 - Maximum property name length exceeded.
- 5973 - Distributed publish/subscribe subscription inhibited
- 5974 - Distributed publish/subscribe publication inhibited
- 6254 - The system could not dynamically load shared library
- 7234 - Number of messages loaded
- 8245 - Entity has insufficient authority to display object
- 9001 - Channel program ended normally
- 9002 - Channel program started
- 9202 - Remote host not available
- 9208 - Error on receive from host
- 9209 - Connection closed
- 9228 - Cannot start channel responder
- 9489 - SVRCONN max instances limit exceeded
- 9490 - SVRCONN max instances per client limit exceeded
- 9508 - Cannot connect to queue manager
- 9524 - Remote queue manager unavailable
- 9528 - User requested closure of channel
- 9545 - Disconnect interval expired
- 9558 - Remote Channel is not available
- 9637 - Channel is lacking a certificate
- 9776 - Channel was blocked by user ID
- 9777 - Channel was blocked by NOACCESS map
- 9782 - Connection was blocked by address
- 9999 - Channel program ended abnormally
If the same message ID is specified in both SuppressMessage and ExcludeMessage, the message is excluded.
This option is not applicable to diagnostic message services defined in MQ client.ini.
- SuppressInterval= length
- Specifies the time interval, in seconds, in which messages specified in SuppressMessage are written to the queue manager error log once only. length must be in the range 1 - 86400 seconds. If SuppressInterval is not specified, the default value of 30 seconds is used.
- Severities
- A comma separated list of severity levels, where the name of the severity level is not case
sensitive. Allowable values are:
- I (or Information or 0)
- W (or Warning or 10)
- E (or Error or 20 and 30)
- S (or Stop or 40)
- T (or System or 50)
Notes:
- The default value is all
- Only messages in the selected severity levels are presented to the service.Alternatively, you
can use the plus character (+) which displays the specified error level, and all
higher levels. For example, to display all errors:
Severities=E+
- Diagnostic message services
The following diagnostic message services and their service specific attributes, specified under the DiagnosticSystemMessages, DiagnosticMessages and DiagnosticMessagesTemplate stanzas of our configuration files can be defined:
Parent topic: Diagnostic message logging
Related reference