Author |
Message
|
martinsu |
Posted: Fri Feb 20, 2004 2:59 am Post subject: Problem connecting W2K (MQ 5.2) with Tandem NSK (MQ 2.2) |
|
|
Newbie
Joined: 20 Feb 2004 Posts: 6
|
Hi,
I need some assistants on getting the communication between my Windows Box (Win 2K with MQ 5.2 installed) and a Tandem NSK (MQ 2.2 installed) to work.
I set up two channels with appropriate XmitQueues and remote queues on both boxes. The channels (Tandem --> Win2K, Win2K --> Tandem) can be started and messages can be sent from both sides and arrive on the other. But:
-- messages from Tandem to Win2K arrive at the correct destination
-- messages from Win2K to Tandem are put to the DeadLetter queue on Tandem with errorcode 2035 (Not Authorized).
I really don't know whats going wrong. I think I did set up all authorizations correct.
Thanks for any help
Martin |
|
Back to top |
|
 |
LuisFer |
Posted: Fri Feb 20, 2004 8:38 am Post subject: Re: Problem connecting W2K (MQ 5.2) with Tandem NSK (MQ 2.2) |
|
|
 Partisan
Joined: 17 Aug 2002 Posts: 302
|
Are you using SAFEGUARD , GUARDIAN or the MQ Security? |
|
Back to top |
|
 |
mqonnet |
Posted: Fri Feb 20, 2004 8:44 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Did you add a principal with the same name as your logged on userid on NT box.
If safeguard is on, then make sure you map it to an MQM user or if you are mapping it to a non-mqm user then you use setmqaut to set authoriziations appropriately.
If not using safeguard then, make sure you setmqaut authorizations on mq objects that you wish to access..
PS: 2.2 is way outdated. Its been out of service for a long time. 5.1 is the latest and i believe 5.3 is the next. When, i am not sure.
Cheers
Kumar |
|
Back to top |
|
 |
LuisFer |
Posted: Fri Feb 20, 2004 9:04 am Post subject: |
|
|
 Partisan
Joined: 17 Aug 2002 Posts: 302
|
Hi Kumar:
The General Avail. of WebSphere MQ V5.3 for NSK will be on the 1Q of 2005 (notice from IBM).
My questión about the type of security was , because we have a lot of problems in the first Installation (V2.2) with Safeguard, ( Subvols not authorized, vols not autorized) & always was the Safeguard. |
|
Back to top |
|
 |
mqonnet |
Posted: Fri Feb 20, 2004 9:14 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Safeguard is primarily a user-based secuirty mechanism and has nothing to do with file security or even vol/subvol security.
If safeguard is on, then you can form groups and assign authorities to the users within that group. If it is not on, then you have to individually assign authorities to each user.
I was not very clear with your question, so just gave a briefing on safeguard, which you might already know.
As for V5.3, i dont think there is any formal announcement/committment yet. I believe they are working towards it. Hope to see it early next year though, as you mentioned.
Cheers
Kumar |
|
Back to top |
|
 |
martinsu |
Posted: Fri Mar 05, 2004 6:47 am Post subject: Did not work until now |
|
|
Newbie
Joined: 20 Feb 2004 Posts: 6
|
Hi,
thanks to all for your help until now. But anyhow, I did not get it to work.
We are using SAFEGUARD on our Tandems, but I set up the MQ-Authority Manager to handle MQ-Series Authorisations.
By
Martin |
|
Back to top |
|
 |
mqonnet |
Posted: Fri Mar 05, 2004 7:58 am Post subject: |
|
|
 Grand Master
Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa.
|
Martin, explain your current problem(if any) in detail. Your last post doesnt really say what the problem is.
Since safeguard is present, all the users in the MQM group would have access to your qm.
Cheers
Kumar |
|
Back to top |
|
 |
|