inhibit events, inhibit, local, local events, remote, remote events, start and stop, events, start and stop events" />
Queue manager events
Queue manager events are related to the use of resources within queue managers, such as an application trying to put a message to a queue that does not exist. The event messages for queue manager events are put on the SYSTEM.ADMIN.QMGR.EVENT queue. The following queue manager event types are supported:
- Authority (on Windows, HP OpenVMS, Compaq NonStop Kernel, and UNIX systems only)
- Inhibit
- Local
- Remote
- Start and stop (z/OS supports only start)
For each event type in this list, there is a queue manager attribute that enables or disables the event type. See the WebSphere MQ Script (MQSC) Command Reference for more information.
The conditions that give rise to the event include:
- 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.
Authority events
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.
Note
- All authority events are valid on HP OpenVMS, Windows, and UNIX systems only.
- Compaq NonStop Kernel only supports Not Authorized (type 1).
For more information about the event data returned in authority event messages see:
Inhibit events
Inhibit events indicate that an MQPUT or MQGET operation has been attempted against a queue, where the queue is inhibited for puts or gets.
For more information about the event data returned in inhibit event messages, see:
Local events
Local events indicate that an application (or the queue manager) has not been able to access a local queue or other local object. For example, an application might try to access an object that has not been defined.
For more information about the event data returned in local event messages, see:
Remote events
Remote events indicate that an application (or the queue manager) cannot access a (remote) queue on another queue manager. For example, the transmission queue to be used might not be correctly defined.
For more information about the event data returned in the remote event messages, see:
- Default Transmission Queue Type Error
- Default Transmission Queue Usage Error
- Queue Type Error
- Remote Queue Name Error
- Transmission Queue Type Error
- Transmission Queue Usage Error
- Unknown Default Transmission Queue
- Unknown Remote Queue Manager
- Unknown Transmission Queue
Start and stop events
Start and stop events (z/OS supports only start) indicate that a queue manager has been started or has been requested to stop or quiesce.
Stop events are not recorded unless the default message-persistence of the SYSTEM.ADMIN.QMGR.EVENT queue is defined as persistent.
For more information about the event data returned in the start and stop event messages, see: