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 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.
On Linux and UNIX systems, the user ID must be a member of the mqbrkrs group.
On Windows platforms, no authorization is required.
BIP8088I: There are no WebSphere MQ Publish/Subscribe neighbors
BIP8089I: WebSphere MQ Publish/Subscribe neighbor <brokername> is inactive.
BIP8090I: WebSphere MQ Publish/Subscribe neighbor <brokername> is active.
BIP8091I: Common stream streamname
mqsilistmqpubsub WBRK_BROKERmight 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.