Stopping the receiver channel on a WebSphere MQ link

You can stop the receiver channel on a WebSphere® MQ link while leaving the link itself running.

Before you begin

Note: If you stop the receiver channel on a WebSphere MQ link, communication with the target WebSphere MQ network on that channel will cease for both point-to-point messaging and publishing and subscribing. Messages will be held at their transmission locations.

You might want to warn the administrator of the WebSphere MQ network that you are about to stop the channel.

About this task

If you stop a receiver channel, messages sent to the WebSphere MQ link engine are not received.

If a WebSphere MQ sender channel is started while an MQ link receiver channel is stopped, the request fails with an error indicating that the receiver channel is not available.

For more information about stopped states of the WebSphere MQ link and its channels, see States of the WebSphere MQ link and its channels.

Procedure

  1. Start the administrative console.
  2. In the navigation pane, click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional properties] WebSphere MQ links -> link_name -> [Additional Properties] Receiver channel .
  3. Select the check box next to the channel you want to stop.
  4. In the Stop mode list, select Quiesce or Force.
  5. In the Target state list, select Inactive or Stopped.
  6. Click Stop.

Results

Stopping a receiver channel stops all the receiver channel connections for that receiver. The resultant state of the receiver channel, and the sender channel in the WebSphere MQ network with which it is communicating, depends on the options you choose:
Table 1. Stop modes
  Stop mode
Quiesce Force
Target state Inactive The receiver channel moves to the stopping state and the data flow to the WebSphere MQ sender channel stops. When the WebSphere MQ sender channel next tries to communicate with the receiver channel the WebSphere MQ sender channel enters a state of retrying. The receiver channel then becomes inactive. The retrying WebSphere MQ sender channel then reestablishes a session with the receiver channel, and both channels become running. The receiver channel immediately becomes inactive. When the WebSphere MQ sender channel next tries to communicate with the receiver channel, the WebSphere MQ sender channel enters a state of retrying. The retrying WebSphere MQ sender channel then reestablishes a session with the receiver channel, and both channels become running.
Stopped The receiver channel moves to the stopping state and the data flow to the WebSphere MQ sender channel stops. When the WebSphere MQ sender channel next tries to communicate with the receiver channel the WebSphere MQ sender channel enters a state of retrying. The receiver channel then becomes stopped, so preventing the WebSphere MQ sender channel from reestablishing a session. The WebSphere MQ sender channel itself then becomes stopped. The receiver channel immediately becomes stopped. When the WebSphere MQ sender channel next tries to communicate with the receiver channel, the WebSphere MQ sender channel enters a state of retrying, and then becomes stopped itself.
Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tjc0036B_
File name: tjc0036B_.html