| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error 2035 |
« View previous topic :: View next topic » |
| Author |
Message
|
| lcarreno |
 Posted: Mon Dec 09, 2002 8:36 am Post subject: Error 2035 |
 |
|
Novice
Joined: 06 Dec 2002
Posts: 20
|
Hello :
I want connect to QManager, Qmanager work in unix, my app is develoment in Visual Basic, i change my var MQSERVER='CHANEL/TCP/ipadress(PORT)' and change in options at type = 2 but when try to connect, the reponse code is 2035
2035 is NOT AUTHORIZED FOR ACCEESS
How i can connect my app ( VISUAL BASIC ) with QM (unix) ? |
|
| Back to top |
|
 |
| nimconsult |
| Posted: Tue Dec 10, 2002 12:05 am Post subject: |
|
|
Master
Joined: 22 May 2002
Posts: 268
Location: NIMCONSULT - Belgium
|
I am not expert in this field but I think that
1)
Either you ensure that your Windows user id matches an existing Unix user id configured with proper MQ Series access.
2)
Or you assign a user id on your server connection channel. This userid must be configured with proper MQ Series access. This one is easier but unsafe because it gives access to every client on your network.
Maybe other persons on this forum will complete/correct this brief answer
Nicolas
_________________
Nicolas Maréchal
Senior Architect - Partner
NIMCONSULT Software Architecture Services (Belgium)
http://www.nimconsult.be |
|
| Back to top |
|
|
| MichaelR |
| Posted: Thu Dec 12, 2002 5:45 am Post subject: Response code 2035 |
|
|
Apprentice
Joined: 20 May 2002
Posts: 37
Location: Tampa
|
There is a little more involved to resolve 2035 retrun codes than just creating the user profile of the same name on UNIX. This is, however, a very important step in the process.
It is also necessary to insure that the "principal" or "group" the user Id is assigned to has permissions to physically "connect" to the QMgr.
Overlooking this layer of MQ security is a common mistake when deploying MQ Client applications.
Alternatively you can take approach #2 as described by NIMCONSULT. I wouldn't recommed to this though unless you are planning to implement MQ Security Exits.
 |
|
| Back to top |
|
|
| blane99 |
| Posted: Mon Dec 16, 2002 10:56 am Post subject: 2035 |
|
|
Apprentice
Joined: 12 Jun 2002
Posts: 41
|
Try the following and do as member of mqm group where QM1=qmgrname ,queue =TESTQ , client's user id is in group called mqdev:
/opt/mqm/bin/setmqaut -m QM1 -t qmgr -g mqdev +connect
/opt/mqm/bin/setmqaut -m QM1 -t queue -n TESTQ -g mqdev +browse +get +put
Always best to specify group name rather than principal. See manual for why. It's important. As the other gentlemen specified, using mcauserid in svrconn channel definition is not a good idea. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
