| Author |
Message
|
| chirasukham |
 Posted: Fri Sep 06, 2013 2:42 am Post subject: MQ error opening topic handle (2035 ?) |
 |
|
Novice
Joined: 07 May 2013
Posts: 19
|
WMB rookie seeks guidance.
A year or so ago, our WMB app was ported from WMB 6.0 to 7.0.
The developer is no longer with us.
I am asked to deliver changes to the app.
The uses Topic/PUblication node.
I have gotten as far as setting up debug, and following through, to try and find the exceptions.
Here is the offending exception List
(copied from debug panel)
UnknownException
File /build/S700_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubEngineNode.cpp
Line 1081
Function ImbPubSubEngineNode::publish
Type ComIbmPSServiceNode
Name src/PIP_UpdateEventHandler#FCMComposite_1_7.ComIbmPublication#FCMComposite_1_1
Label src.XXXXXXXXXXXXXXXXXX
Catalog BIPmsgs
Severity 3
Number 7122
Text MQ error opening topic handle
Insert
Type 2
Text 2035
Insert
Type 5
Text /nnn/saveXXXXXXX
Insert
Type 2
Text 2
The flow appears to be working well, and the exception occurs when the flow wants to post the message to the Publication node. MQ admins are able to post to the node. If I understand the exception list correctly, 2035 in mqrc says authorization not available.
The flow is ported from WMB 6.0., where it was working beautifully.
I looked at other postings on this subject, and copied and pasted the MQRFH2 statements to set Topic and Command, but no luck.
Is this really an authorizations issue ? Or should I be looking elsewhere ?
Thanks |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Sep 06, 2013 3:06 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Dear WMB Rookie :
1. Please use code tags.
2. Trust your stack trace, yes, 2035 is the root cause (there may be others that show up after you solve that one).
3. Trace nodes and defects are your friends.
Signed,
LostInLosAngeles
a. k. a.
Lancelot Linc
P. S. Good luck with the rest of your port. It's really not so difficult once you get past the initial errors.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Tibor |
| Posted: Fri Sep 06, 2013 5:50 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| WMB v7 uses the Pub/Sub functionality of WMQ v7 for Publish-Subscribe tasks. So you could find the reason of this error at MQ level - if your MQ version is v7.1 or above, security errors are logged in AMQERR0x.LOG files, too. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 06, 2013 5:57 am Post subject: Re: MQ error opening topic handle (2035 ?) |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| chirasukham wrote: |
| Is this really an authorizations issue ? |
It really is an authorisations issue. That's why your MQ admins can post.
WMBv6.n did it's own pub/sub. WMBv7 uses the pub/sub built into the queue manager. So the fact that the flow works beautifully in WMBv6 has no relevance to running it on WMBv7 & the configuration (including security) that you need.
Note also that pub/sub was reworked between WMQv6 & v7
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 06, 2013 5:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Tibor wrote: |
| WMB v7 uses the Pub/Sub functionality of WMQ v7 for Publish-Subscribe tasks. So you could find the reason of this error at MQ level - if your MQ version is v7.1 or above, security errors are logged in AMQERR0x.LOG files, too. |
The reason is very very clear and straight forward.
The userid being presented by the publication node is not authorized to publish.
That is the reason for this error.
The reason this error is confusing is because the Publication node does not act like the MQOutput node. It doesn't use the broker service ID to talk to MQ. |
|
| Back to top |
|
|
| chirasukham |
| Posted: Fri Sep 06, 2013 7:03 am Post subject: Topic handle error |
|
|
Novice
Joined: 07 May 2013
Posts: 19
|
Now I know why this is "THE" site for MQ/WMB... Thanks to all for caring and replying so quickly. I now know to "Trust the Exception List", (Except I need more practice reading the darned thing.. Wish some one would make it more easy to read.. but then its easier than reading "C" core dumps.. ) 
I'll follow up with MQ Admins.
P.S. The key post that caught my attention.. I must have access to PUBLISH to the node.. Back to IBM docs to find the various access modes for Publication nodes.
Thanks so much. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 06, 2013 7:25 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
No, you just need to clear the user from the output message given to the publication node.
Then it will use the broker userid, which has to be a member of mqm. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 06, 2013 7:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Then it will use the broker userid, which has to be a member of mqm. |
No it doesn't; it just typically is in any normal world.
Unlike mine. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Tibor |
| Posted: Fri Sep 06, 2013 7:30 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| mqjeff wrote: |
| No, you just need to clear the user from the output message given to the publication node. |
Another option is adding +setid (and +pub) permission for that user. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 06, 2013 7:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| Then it will use the broker userid, which has to be a member of mqm. |
No it doesn't; it just typically is in any normal world. |
Regardless, the publication node uses the message to determine what ID is presented to MQ. If the userid in the message is blank, then the broker service id is used. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Sep 06, 2013 7:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Vitor wrote: |
| mqjeff wrote: |
| Then it will use the broker userid, which has to be a member of mqm. |
No it doesn't; it just typically is in any normal world. |
Regardless, the publication node uses the message to determine what ID is presented to MQ. If the userid in the message is blank, then the broker service id is used. |
Quite, and this is relevant to the OP's problem. I was just covering the circumstance that the OP is in the 1% of sites that don't put the broker service id in the mqm group & to prevent a hare running that it had to be in the mqm group.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| chirasukham |
| Posted: Fri Sep 06, 2013 1:11 pm Post subject: Problem solved. (doh!). we had not defined the topic lists. |
|
|
Novice
Joined: 07 May 2013
Posts: 19
|
Admins resolved the issue on. their side. I think the Topic string list was incomplete, so a few topics were failing.
Thanks for all the info.
What is normal etiquette for closing a string ?
K |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Sep 07, 2013 6:07 am Post subject: Re: Problem solved. (doh!). we had not defined the topic li |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| chirasukham wrote: |
What is normal etiquette for closing a string ?
K |
adding resolved or closed in the subject line of the 1st post
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mgk |
| Posted: Sat Sep 07, 2013 6:40 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| What is normal etiquette for closing a string ? |
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| dogorsy |
| Posted: Sat Sep 07, 2013 9:56 pm Post subject: |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
Brilliant!  |
|
| Back to top |
|
|
|
|
