Channel and bridge events

Channel events are reported by channels as a result of conditions detected during their operation, such as when a channel instance is stopped. The event messages for channel and bridge events are put on the SYSTEM.ADMIN.CHANNEL.EVENT queue. Channel events are generated:

• By a command to start or stop 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, runmqchl, or a queue manager trigger message does not generate an event; in this case the only event generated is 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 to an event queue, an error condition causes the queue manager to create an event as usual.

For more information about the event data returned in the channel event messages, see:

• Channel Activated

• Channel Auto-definition Error

• Channel Auto-definition OK

• Channel Conversion Error

• Channel Not Activated

• Channel Started

• Channel Stopped

• Channel Stopped By User

 

IMS bridge events (z/OS only)

These events are reported when an IMS bridge starts or stops.

For more information about the event data returned in the messages specific to IMS bridge events, see

• Bridge Started

• Bridge Stopped

 

SSL events

The only SSL event is the Channel SSL Error event. This event is reported when a channel using the Secure Sockets Layer (SSL) fails to establish an SSL connection.

For more information about the event data returned in the message specific to the SSL event, see Channel SSL Error