Channel and bridge events
Channels report these events as a result of conditions detected during their operation. For example, when a channel instance is stopped.
Channel events are generated in the following circumstances:
- When a command starts or stops a channel.
- When a channel instance starts or stops.
- When a channel receives a conversion error warning when getting a message.
- When an attempt is made to create a channel automatically; the event is generated whether the attempt succeeds or fails.
Note: Client connections do not cause Channel Started or Channel Stopped events.
When a command is used to start a channel, an event is generated. Another event is generated when the channel instance starts. However, starting a channel by a listener, the runmqchl command, or a queue manager trigger message does not generate an event. In these cases, an event is generated only when the channel instance starts.
A successful start or stop channel command generates at least two events. These events are generated for both queue managers connected by the channel (providing they support events).
If a channel event is put on an event queue, an error condition causes the queue manager to create an event.
The event messages for channel and bridge events are put on the SYSTEM.ADMIN.CHANNEL.EVENT queue.
The channel event messages can contain the following event data:
- Channel Activated
- Channel Auto-definition Error
- Channel Auto-definition OK
- Channel Conversion Error
- Channel Not Activated
- Channel Started
- Channel Stopped
- Channel Stopped By User
- Channel Blocked
IMS bridge events ( z/OS only)
These events are reported when an IMS bridge starts or stops.
The IMS bridge event messages can contain the following event data:
SSL events
The only TLS event is the Channel SSL Error event. This event is reported when a channel using TLS fails to establish a TLS connection.
The SSL event messages can contain the following event data:
Parent topic: Event types