Queue manager events
Queue manager events are related to the use of resources within queue managers. For example, a queue manager event is generated if an application tries to put a message on a queue that does not exist.
The following examples show conditions that can cause a queue manager event:
- An application issues an MQI call that fails. The reason code from the call is the same as the reason code in the event message.
A similar condition can occur during the internal operation of a queue manager; for example, when generating a report message. The reason code in an event message might match an MQI reason code, even though it is not associated with any application. Do not assume that, because an event message reason code looks like an MQI reason code, the event was necessarily caused by an unsuccessful MQI call from an application.
- A command is issued to a queue manager and processing this command causes an event. For example:
- A queue manager is stopped or started.
- A command is issued where the associated user ID is not authorized for that command.
IBM® MQ puts messages for queue manager events on the SYSTEM.ADMIN.QMGR.EVENT queue, and supports the following queue manager event types:
- Authority (on AIX®, Linux®, and Windows only)
- Authority events report an authorization, such as an application trying to open a queue for
which it does not have the required authority, or a command being issued from a user ID that does
not have the required authority. The authority event message can contain the following event data:
- Not Authorized (type 1)
- Not Authorized (type 2)
- Not Authorized (type 3)
- Not Authorized (type 4)
- Not Authorized (type 5)
- Not Authorized (type 6)
All authority events are valid on AIX, Linux, and Windows only.
- Inhibit events indicate that an MQPUT or MQGET operation has been attempted against a queue where the queue is inhibited for puts or gets, or against a topic where the topic is inhibited for publishes. The inhibit event message can contain the following event data:
- When an application or the queue manager has not been able to access a local queue or other local object, for example, because the object has not been defined, the queue manager can generate a local event message. The local event message can contain the following event data:
- When an application or the queue manager cannot access a remote queue on another queue manager, for example, the transmission queue is not correctly defined, the queue manager can generate a remote event message. The remote event message can contain the following event data:
- Start and stop
- Start and stop events indicate that a queue manager has been started or has been requested to
stop or quiesce.
z/OS® supports only start events.
Stop events are not recorded unless the default message-persistence of the SYSTEM.ADMIN.QMGR.EVENT queue is defined as persistent. The start and stop event message can contain the following event data:
For each event type in this list, you can set a queue manager attribute to enable or disable the event type.