| Author |
Message
|
| varmamvn |
 Posted: Sun Apr 07, 2002 11:25 pm Post subject: |
 |
|
Novice
Joined: 16 Mar 2002
Posts: 21
|
Hi all,
Recently, my Sun Solaris admin changed the userId that I'm supposed to work in.
My MQ Series Base Java application used to work fine earlier with my old Id. I gave a setmqaut for the Queue Manager and all the queues that my application uses. I have now done the same for the new UserID. I have given "+all permission" for the new userId for the Queue Manager and all the queues. But still I get a Reason Code 2035 when I connect to the Q Manager. I have even tried a "Refresh Security" from the Runmqsc prompt. I fail to understand why it fails for the new User Id, when it worked for the old userId.
Can you please point me in the right direction?
Many thanks
Varma |
|
| Back to top |
|
 |
| StefanSievert |
| Posted: Mon Apr 08, 2002 2:15 am Post subject: |
|
|
Partisan
Joined: 28 Oct 2001
Posts: 333
Location: San Francisco
|
I am not 100% sure here, but I think you have to restart your queue manager, if you have added a new userId to the OS. TTBOMK, refresh security only refreshes authorization changes to existing userId's.
It might be worth to try it if you can.
Stefan
_________________
Stefan Sievert
IBM Certified * WebSphere MQ |
|
| Back to top |
|
|
| varmamvn |
| Posted: Mon Apr 08, 2002 7:57 pm Post subject: |
|
|
Novice
Joined: 16 Mar 2002
Posts: 21
|
Thanks Stefan,
Sure, I did restart the Queue Manager and did a Refresh Security already. It still does not work.
Thanks
Varma |
|
| Back to top |
|
|
| gye |
| Posted: Tue Apr 09, 2002 2:02 am Post subject: |
|
|
Novice
Joined: 07 Apr 2002
Posts: 13
|
I think you are using channel as well. In the channel definition there is MCAUSER, which I guess will stand for the principal of the connection. You need to change that accordingly.
Any way, I am new to MQ. You just try |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Apr 09, 2002 10:08 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
If your java app is connecting to the QM as a client, then you need to make sure that the Userid that is being mapped to as principal on Solaris is EXACTLY the same as the one which is coming into the QM through your Java app. And exactly means exactly. If you are logged in as "Fred", your userid/principal on Solaris MUST BE "Fred" and neither "fred" nor "FRED". This value is case sensitive.
Hope this helps.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| varmamvn |
| Posted: Mon Apr 15, 2002 7:54 pm Post subject: |
|
|
Novice
Joined: 16 Mar 2002
Posts: 21
|
Thanks for your suggestions,
But still the problem persists. I mention the userId in the setmqaut principal as exactly the same. I do know that it is case-sensitive.
Any help would be appreciated.
thanks
Varma |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Apr 16, 2002 4:35 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Giving just +all WILL NOT ALLOW ACCESS. For accessing a Qmgr object, you need to allow a few more permissions, which include "connect,altusr and a few more". I keep forgetting this. Please play with the Authorities and would appreciate if you post the MINIMUM required attributes to be set with SETMQAUT for a non-mqm userid. I think they are 3/4 of them.
Hope this helps.
Cheers.
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
|
|
