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 Multiplatforms only)

For Long Term Support and Continuous Delivery before IBM MQ 9.4.3, authority events report unsuccessful authorizations 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. Authority events are controlled through the queue manager AUTHOREV setting.

From IBM MQ 9.4.3, authority events can report successful and unsuccessful authorizations. Authority events report an authorization, such as an application trying to open a queue for which it does or does not have the required authority, or a command being issued from a user ID that does not have the required authority. Authority events are controlled through the queue manager AUTHOREV and AUTHEVSC settings.

The authority event message can contain the following event data.

The following authority events are produced so long as the queue manager authority event setting (AUTHOREV) is ENABLED:

• Not Authorized (type 1)
• Not Authorized (type 2)
• Not Authorized (type 3)
• Not Authorized (type 4)
• Not Authorized (type 5)
• Not Authorized (type 6)

The following authority events are produced as long as the queue manager authority event setting (AUTHOREV) is ENABLED and the queue manager authority event scope setting (AUTHEVSC) is at least ALLCONNS:

• Authorized (type 1)

The following authority events are produced as long as the queue manager authority event setting (AUTHOREV) is ENABLED and the queue manager authority event scope setting (AUTHEVSC) is ALLCHECKS:

• Authorized (type 2)
• Authorized (type 3)
• Authorized (type 4)

Authorized (type 2) event messages could be produced in large quantities where a lot the event messages produced are duplicates of each other. To reduce the number of duplicates a system to rate limit duplicate event messages is available. For more information see Limiting the rate of positive authority events.

Authority events can be linked together by examining the MQBACF_CONN_TAG and MQBACF_CONNECTION_ID fields. These fields are identical for event messages produced by the same application connection.

All authority events are valid on Multiplatforms only.

Inhibit

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. Inhibit events are controlled through the queue manager INHIBTEV setting. The inhibit event message can contain the following event data:

• Get Inhibited
• Put Inhibited

Local

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. Local events are controlled through the queue manager LOCALEV setting. The local event message can contain the following event data:

• Alias Base Queue Type Error
• Unknown Alias Base Queue
• Unknown Object Name

Remote

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. Remote events are controlled through the queue manager REMOTEEV setting. The remote event message can contain the following event data:

• 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

Start and stop events indicate that a queue manager has been started or has been requested to stop or quiesce. Start and Stop events are controlled through the queue manager STRSTPEV setting.

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:

• Queue Manager Active
• Queue Manager Not Active

For each event type in this list, you can set a queue manager attribute to enable or disable the event type.