ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » Omegamon-Msg Delete/ forward - 2035(NOT_AUTHORIZED) error

Post new topic  Reply to topic Goto page Previous  1, 2
 Omegamon-Msg Delete/ forward - 2035(NOT_AUTHORIZED) error « View previous topic :: View next topic » 
Author Message
exerk
PostPosted: Sun Dec 12, 2010 4:02 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

And as I am fond of pointing out, THIS is often very, very helpful...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
chris boehnke
PostPosted: Sun Dec 12, 2010 5:36 pm    Post subject: Reply with quote

Partisan

Joined: 25 Jul 2006
Posts: 369

fjb_saper wrote:
Quote:
Yes, the "TEPUser" is part of mqm group on the solaris machine where the Qmgr/ agent is running. The "TEPUSER"(uppercase) doesn't have perms. When I turn on MQ traces and look at the traces, I see the user as TEPUSER(uppercase). When the TEPUser is trying to DELETE/ FORWARD, I see the user passed to the MQ manager is TEPUSER(in upper case). How to pass the original user id from TEPS client to the QMgr from TEPS console (TEPUser)?.

We are under the process of upgrading to version 7 but right now the monitoring agent should function properly in DELETE/ FORWARD functions. I can open a PMR but I just want to make sure we are not missing anything with our setup.

I remember there were some case problems for the userid in the early versions of 6.0 especially from windows to Unix. Upgrade to the latest of 6.0.

Have fun

You must be talking about this link: https://www-304.ibm.com/support/docview.wss?rs=171&uid=swg1IC49533

Let me know.

Thanks.
Back to top
View user's profile Send private message
chris boehnke
PostPosted: Sun Dec 12, 2010 5:38 pm    Post subject: Reply with quote

Partisan

Joined: 25 Jul 2006
Posts: 369

exerk wrote:
And as I am fond of pointing out, THIS is often very, very helpful...


I will try this out and let you know. Thanks.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sun Dec 12, 2010 11:34 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY

chris boehnke wrote:

You must be talking about this link: https://www-304.ibm.com/support/docview.wss?rs=171&uid=swg1IC49533

Let me know.

Thanks.

Yes I was. Looks like this is already fixed in your version. However it is unusual in Unix to have mixed case user ids. Can you try with a lower case userid all around?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
chris boehnke
PostPosted: Mon Dec 13, 2010 1:27 pm    Post subject: Reply with quote

Partisan

Joined: 25 Jul 2006
Posts: 369

fjb_saper wrote:
chris boehnke wrote:

You must be talking about this link: https://www-304.ibm.com/support/docview.wss?rs=171&uid=swg1IC49533

Let me know.

Thanks.

Yes I was. Looks like this is already fixed in your version. However it is unusual in Unix to have mixed case user ids. Can you try with a lower case userid all around?

I tried with a different user id which is all the lowercase and still see the same issue.
When we try to DELETE the msgs from a mainframe queue manager from TEPS client, it works but not for midranges.

We opened a pmr with IBM. Will let you know what IBM says.

Thanks for your help.
Back to top
View user's profile Send private message
ramires
PostPosted: Mon Dec 13, 2010 2:56 pm    Post subject: Reply with quote

Knight

Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa

Is a client channel involved? Are you specifying an mcauser in that channel? I did not understand how the windows box "talks" to the solaris box. In the traces you did can you find entries for the "TEPUser" when browsing a queue on the server?
Back to top
View user's profile Send private message
chris boehnke
PostPosted: Tue Jan 04, 2011 7:33 pm    Post subject: Reply with quote

Partisan

Joined: 25 Jul 2006
Posts: 369

We contacted IBM and IBM says there is a bug in TEMS 6.2. This issue was not there in the earlier versions of TEMS.

There will be a fix available in Jan.2011 to resolve this issue.

Thanks.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jan 04, 2011 9:16 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY

Thanks for updating the thread Chris.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum Index » General Discussion » Omegamon-Msg Delete/ forward - 2035(NOT_AUTHORIZED) error
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.