| Author |
Message
|
| fajifazeel |
 Posted: Mon Mar 05, 2012 2:23 am Post subject: Reason 2035 |
 |
|
Newbie
Joined: 05 Mar 2012
Posts: 6
Location: DXB
|
HI guyzz...
help me out this "Reason 2035"
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2035'.
y this occurs wen running message flow....
i made a message flow for accessing database...and ran setpara.....command
wat else i hav to do solve dis prob.... |
|
| Back to top |
|
 |
| mqsiuser |
| Posted: Mon Mar 05, 2012 3:31 am Post subject: Re: Reason 2035 |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
Check out the List of MQ Reason codes and in your special case: http://www-01.ibm.com/support/docview.wss?uid=swg21166937
Either you need to be a user who is in the mqm group, or you are setting the permissions with setmqaut commands.
But honestly I am not an expert for that and there are others that know MQ(-security) better than me.
Also: Search around (on Google) and probably (MQ) training could be advisable.
2012-03-05: "amqs..." --> "setmqaut"
_________________
Just use REFERENCEs
Last edited by mqsiuser on Mon Mar 05, 2012 7:58 am; edited 1 time in total |
|
| Back to top |
|
|
| rammer |
| Posted: Mon Mar 05, 2012 3:36 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| What permissions are you setting? |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Mon Mar 05, 2012 3:42 am Post subject: |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
check whether you broker user is in the mqm group... If not add him.
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 05, 2012 6:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqsiuser wrote: |
| check whether you broker user is in the mqm group... If not add him. |
Having first checked that your site security standards allow the broker user to be a member of mqm; there's no technical requirement for this to be the case. The membership could have been omitted deliberately.
It's also not a good idea to get into the habit of fixing 2035 errors by putting the user into mqm. The broker's service user is something of an exception but by and large no end user should have that membership. Much better to provide the necessary authorizations in a limited, audited and controlled fashion.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rammer |
| Posted: Mon Mar 05, 2012 7:15 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
Hi, can you explain this please
<<The broker's service user is something of an exception>>
The reason I ask is that I don't have much to do with MB but notice that on all our MQ installations where MB is present the MB account is a memeber of the MQ Group.
Default of all other applications I set up is to set the correct permissions on the Queue Manager, Queue's and Channel using MCAUSER etc and not to add anything into mqm group.
thanks |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 05, 2012 7:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rammer wrote: |
Hi, can you explain this please
<<The broker's service user is something of an exception>>
The reason I ask is that I don't have much to do with MB but notice that on all our MQ installations where MB is present the MB account is a memeber of the MQ Group. |
It's a technical requirement for the broker service user. |
|
| Back to top |
|
|
| rammer |
| Posted: Mon Mar 05, 2012 7:24 am Post subject: |
|
|
Partisan
Joined: 02 May 2002
Posts: 359
Location: England
|
| mqjeff wrote: |
| rammer wrote: |
Hi, can you explain this please
<<The broker's service user is something of an exception>>
The reason I ask is that I don't have much to do with MB but notice that on all our MQ installations where MB is present the MB account is a memeber of the MQ Group. |
It's a technical requirement for the broker service user. |
Thank you |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 05, 2012 7:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| rammer wrote: |
The reason I ask is that I don't have much to do with MB but notice that on all our MQ installations where MB is present the MB account is a memeber of the MQ Group.
Default of all other applications I set up is to set the correct permissions on the Queue Manager, Queue's and Channel using MCAUSER etc and not to add anything into mqm group. |
This is very much the traditional position. What I meant was that no non-WMQ administering user id should be a member of the mqm group; applications trying to use queue should have their permissions set up in exactly the way you describe.
While the broker's service id (and WMB itself) is in essence only an application trying to use queue facilities it's an exception in that for convienience it's usually in the mqm group so you don't need to add permissions for each queue you use in a flow.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Mar 05, 2012 7:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| It's a technical requirement for the broker service user. |
With respect, no it isn't. It's a requirement when the broker is created but the reason it needs the authority then is because as part of the creation process it's not only issuing the commands to create all the queues required for the broker's operation, it's issuing setmqaut commands for those objects as well on the mqbrkrs group.
So the broker will run perfectly fine without mqm group membership. It's not required for operation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Mar 05, 2012 7:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| It's a technical requirement for the broker service user. |
With respect, no it isn't. It's a requirement when the broker is created but the reason it needs the authority then is because as part of the creation process it's not only issuing the commands to create all the queues required for the broker's operation, it's issuing setmqaut commands for those objects as well on the mqbrkrs group.
So the broker will run perfectly fine without mqm group membership. It's not required for operation. |
  |
|
| Back to top |
|
|
| fajifazeel |
| Posted: Mon Mar 05, 2012 11:32 pm Post subject: bt still showing "Reaoson 2035" |
|
|
Newbie
Joined: 05 Mar 2012
Posts: 6
Location: DXB
|
I'm on wmb v7....
did authorization of queues
bt still showing "Reaoson 2035"
i can run the flow wen it is a local broker
bt wen i try to a rempote one i cant .....how to solve?
_________________
FG |
|
| Back to top |
|
|
| mqsiuser |
| Posted: Tue Mar 06, 2012 1:01 am Post subject: Re: bt still showing "Reaoson 2035" |
|
|
Yatiri
Joined: 15 Apr 2008
Posts: 637
Location: Germany
|
On the remote AIX/Unix/Linux (!?!) box tell an AIX/Unix/Linux admin to "add the broker user (e.g. mqsibrk) to the mqm group".
The things mqjeff/vitor talk about is advanced stuff (likely its o.k. for your site to put in the broker user into mqm)
If it would be not ok, then the AIX/Unix/Linux Admin should tell you that (also recheck with management)
_________________
Just use REFERENCEs |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 06, 2012 5:37 am Post subject: Re: bt still showing "Reaoson 2035" |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqsiuser wrote: |
| The things mqjeff/vitor talk about is advanced stuff (likely its o.k. for your site to put in the broker user into mqm) |
No it isn't!!!! 
That's a basic installation / configuration decision, and documented. You either have the broker id in mqm or you don't.
There's nothing advanced about group membership.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 06, 2012 5:42 am Post subject: Re: bt still showing "Reaoson 2035" |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fajifazeel wrote: |
i can run the flow wen it is a local broker
bt wen i try to a rempote one i cant .....how to solve? |
Ok, let's take a step back. All flows run on a "local" broker; you can't client a flow onto a remote broker like a JMS application can client onto a remote queue manager.
So you need to explain 2 things before we can help:
- what do you mean by a "remote" broker?
- what exactly is producing the 2035?
Having another look at your original post that 2035 is coming from a JMS component, which broker doesn't use for it's WMQ access. So I'm sitting here wondering if you've got a JCN that accesses a queue directly and that doesn't work unless it's running on your local broker.
I'm also unclear what a 2035 has to do with accessing a database but I plan to let that slide for now.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
