WebSphere Message Brokers
File: an07340_
Writer: Bill Oppenheimer

Reference topic

This build: July 31, 2007 21:33:35

mqsilistmqpubsub command

Supported platforms

Purpose

Use the mqsilistmqpubsub command to display the status of the WebSphere MQ Publish/Subscribe neighbor brokers to the specified WebSphere Message Broker broker.

This command indicates the status of the activity started by a previous join request (see mqsijoinmqpubsub command). The command reports on the status of each neighbor broker, which can be:
Active
Broker status is active if the join request has completed successfully.
Inactive
Broker status is inactive if the join has been initiated, but has not completed.

This command also shows the streams that are recognized by both the WebSphere Message Broker broker and its neighbor (on which messages can be published and distributed between the brokers). Stream information is provided only for neighbors with active status.

Use this command only if you are integrating with, or migrating from, an WebSphere MQ Publish/Subscribe broker network.

The output generated by this command is directed to stdout.

Syntax

Parameters

BrokerName
(Required) The name of the broker for which you want a list of neighbors.

Authorization

On Linux and UNIX systems, the user ID must be a member of the mqbrkrs group.

On Windows platforms, no authorization is required.

Examples

If there are no WebSphere MQ Publish/Subscribe brokers, and no mqsijoinmqpubsub command has been issued, this command returns the following message:
BIP8088I: There are no WebSphere MQ Publish/Subscribe neighbors
If an mqsijoinmqpubsub command has been issued, one of two response messages is displayed:
  • For every broker that is an inactive neighbor of WBRK_BROKER (that is, a request has been made, using the mqsijoinmqpubsub or strmqbrk command, to add the broker to the network, but negotiations for common streams are still in progress), the following message is displayed:
    BIP8089I: WebSphere MQ Publish/Subscribe neighbor <brokername> is inactive.
  • For every broker that is an active neighbor of WBRK_BROKER (that is, the two brokers are exchanging publications and subscriptions for each of the common streams), the following message is displayed:
    BIP8090I: WebSphere MQ Publish/Subscribe neighbor <brokername> is active.
    Additional messages are displayed for active brokers to indicate the common streams for which publications and subscriptions are exchanged, in the following form:
    BIP8091I:   Common stream  streamname
For example,
mqsilistmqpubsub WBRK_BROKER
might return the following responses:
BIP8090I: MQSeries Publish/Subscribe neighbor MQPS_BROKER_1 is active.
BIP8091I:    Common stream SYSTEM.BROKER.DEFAULT.STREAM.
BIP8091I:    Common stream STREAM0.
BIP8090I: MQSeries Publish/Subscribe neighbor MQPS_BROKER_2 is active.
BIP8091I:    Common stream SYSTEM.BROKER.DEFAULT.STREAM.
BIP8091I:    Common stream STREAM150.
BIP8089I: MQSeries Publish/Subscribe neighbor MQPS_BROKER_3 is inactive.

In this example, the WebSphere Message Broker broker has three WebSphere MQ Publish/Subscribe neighbors. Two of these neighbors are active and have been successfully joined to the WebSphere Message Broker broker. The third is inactive and is in the process of being joined.

The list of streams that are common to the WebSphere Message Broker broker and the two active WebSphere MQ Publish/Subscribe brokers are included in the response. For MQPS_BROKER_1, the streams SYSTEM.BROKER.DEFAULT.STREAM and STREAM0 are common. For MQPS_BROKER_2, the streams SYSTEM.BROKER.DEFAULT.STREAM and STREAM150 are common.

If a neighbor is inactive for a long period of time, it is likely that the communication link between the two brokers has been broken. Ensure that the WebSphere MQ connections between the two brokers (channels and transmission queues) are running, and that the WebSphere Message Broker and WebSphere MQ Publish/Subscribe brokers are both active.

Related concepts
Publish/Subscribe
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:33:35

an07340_ This topic's URL is: