| Author |
Message
|
| witteb |
 Posted: Thu Dec 13, 2012 10:48 am Post subject: subscribing to accounting / statistics messages MB 6.1 |
 |
|
Newbie
Joined: 13 Dec 2012
Posts: 3
|
I am having trouble with a new setup - we are running WMQ 6.0 and WMB 6.1. We have installed the components deployed some of the sample flows, enabled the stats, but can't seem to get the subscription to work to pick them up when type is set to XML.
We based our sample program on the IBM Soccer sample listener, essentially setting this up to subscribe to the stats messages. This is where we are really confused.
1. The soccer game works, when we start the broker in WMQ 6.0 (with no WMB broker defined)
2. If we create a WMB, the soccer game fails to work.
3. Stats work if we send them to the log
Any ideas on what is going wrong? I would expect the Soccer game to work with the WMB as an easy way to confirm pub/sub is working - but clearly we haven't done something correctly. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Dec 13, 2012 11:08 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
>>clearly we haven't done something correctly.
You are using versions that are end-of-life. Upgrade to V8.
V6 is no longer supported or maintained.
Pub/sub changed dramatically at V7, so any solution you come up with will not apply on V7 or V8
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 13, 2012 11:11 am Post subject: Re: subscribing to accounting / statistics messages MB 6.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| witteb wrote: |
| we haven't done something correctly. |
Well you've not correctly selected the levels of software for a new installation. WMQv6 is out of support and WMBv6.1 is 2 major levels back. Also one of the big changes in WMBv7/WMQv7 is pub/sub improvement, so if that's what you're planning to use it's a better choice.
And that's irrespective of the additional good stuff WMBv8 adds.
As to what's up with your set up, it's impossible to say from "fails to work". Error messages, reason codes? What have you done to identify and resolve the problem?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 13, 2012 11:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| V6 is no longer supported or maintained. |
For clarity WMBv6.1 is supported; WMBv6.0 is not.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Dec 13, 2012 11:13 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| lancelotlinc wrote: |
| V6 is no longer supported or maintained. |
For clarity WMBv6.1 is supported; WMBv6.0 is not. |
The clock is ticking. V6.1 will not be supported in 263 days, 4 hours, and 13 minutes. Unless an extended support contract is purchased.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 13, 2012 11:23 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Vitor wrote: |
| lancelotlinc wrote: |
| V6 is no longer supported or maintained. |
For clarity WMBv6.1 is supported; WMBv6.0 is not. |
The clock is ticking. V6.1 will not be supported in 263 days, 4 hours, and 13 minutes. Unless an extended support contract is purchased. |
So in 264 days your statement will be correct. But not now.
And there's nothing wrong with your point that Everythingv7 changed how pub/sub worked. Indeed, I made a similar point.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| witteb |
| Posted: Thu Dec 13, 2012 11:40 am Post subject: |
|
|
Newbie
Joined: 13 Dec 2012
Posts: 3
|
I understand that the versions are out of support. Unfortunately, I don't have control over that as much as we have fought. Client has these versions so we are stuck.
Our program flow is doing the following:
1. Put control message registering subscription for $SYS/Broker/ etc... per documentation.
2. Get <OK> in response to subscription request.
3. On subscription, SYSTEM.BROKER.ADMIN.REPLY was specified as the queue.
4. We confirmed subscription on Broker using MQSIBROWSE command on broker.
5. MQGET calls return 2033 errors when looping waiting for messages
One thing that we are confused about and can't find good explanation in IBM documentation is the relationship between the WMQ broker and the WMB broker. Are we supposed to use one or the other? In these old versions, do we need to run "runmqbrk -qm" on the QM we have associated with our WMB Broker? Obviously to start our WMB Broker we need to run "mqsistart ..." to start the broker but the docs don't seem to be clear....
Side note, we did not enable the user name server, which from the documentation we understand this simply adds authentication to the topic subscription service.
Thanks for the help - it is really appreciated! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Dec 13, 2012 11:49 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| witteb wrote: |
| One thing that we are confused about and can't find good explanation in IBM documentation is the relationship between the WMQ broker and the WMB broker. Are we supposed to use one or the other? |
Under this version yes. Version 7 removed the pub/sub from WMB and moved it into the new and highly enhanced pub/sub in WMQv7.
| witteb wrote: |
| Client has these versions so we are stuck |
You should ensure your client understands their version of WMQ is out of support, WMB will be in the foreseable future and whatever they're paying you to develop will need rework when they move.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| witteb |
| Posted: Thu Dec 13, 2012 5:44 pm Post subject: |
|
|
Newbie
Joined: 13 Dec 2012
Posts: 3
|
Thank you - we have notified our customer and will be working with them on their upgrade. This will take time.
With regards to subscribing to the statistics, we have made progress. We are deploying on AIX 6.1.
Our C program is now registering the subcription with the broker. We have confirmed this with both a PSCR response of OK, we have also confirmed with the mqsibrowse command.
When issuing the MQGET for the message, we get CompCode 2 - Reason 2033, which is no message.
If we have done this correctly, should with our subscription issued, the broker place the stats message in our Subscription Queue defined on the subscription?
If more data is helpful, I can post - we modeled our subscriber after the "soccerresults" sample.
thanks again - |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Dec 14, 2012 12:44 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you actually enable the collection of the stats for a one or more flow?
If you don't do this then you won't get any data.
Hint
| Code: |
mqsichangeflowstats $Broker ...
mqsireportflowstats $Broker ...
|
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 14, 2012 5:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| witteb wrote: |
.
3. On subscription, SYSTEM.BROKER.ADMIN.REPLY was specified as the queue.
Thanks for the help - it is really appreciated! |
Don't use the SYSTEM.BROKER.ADMIN.REPLY queue as the destination for a subscription. There are other processes reading from that queue.
In fact don't use any SYSTEM queue as the Destination of a subscription.
Change the subscription destination to a non SYSTEM queue,
Make sure you enabled the statistics on the flow.
You should then get the messages to the subscription destination.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
