| Author |
Message
|
| basha |
 Posted: Tue Aug 16, 2005 9:19 am Post subject: support packs to substitute RFHUtil |
 |
|
Apprentice
Joined: 25 Apr 2004
Posts: 31
|
Hi all,
I am not in the mqm group but am in a group that can has +allmqi authorizations on some apecified queues. Is there a support pack that allows me to connect to the remote qmgr to put/browse/get in/from queues. I think RFHUtil doesnot allow me to do this ...
Thanks,
basha |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Aug 16, 2005 9:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
RFHUtil comes in two flavors, RFHUtil and RFHUtilC.
C stands for "client".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| basha |
| Posted: Tue Aug 16, 2005 9:56 am Post subject: |
|
|
Apprentice
Joined: 25 Apr 2004
Posts: 31
|
Yes,
even though if I use RFHUTILC, can I connect to the queue manager without being in the MQM group? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 16, 2005 10:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If any client connection can be established with your id, then RFHUTILC will work.
Almost all client connections in real world situations are established using IDs that are not in the mqm group - because there's no reason to give away the farm when you just want to sell some cheese.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| basha |
| Posted: Wed Aug 17, 2005 5:36 am Post subject: |
|
|
Apprentice
Joined: 25 Apr 2004
Posts: 31
|
With all repect,
Jeff, I think it doesnot seem to be working. I trieed that with my colleague. I added him into a group called TEST and had setmqaut with +all / +alladm permissions and tested with RFHUTILC. The error: Not authorized shows up. But it seems to work when I add him to mqm group. Am I missing some thing here ?
Basha |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 17, 2005 5:40 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can use setmqaut to authorize a particular user to specific resources on a queue manager.
Any user in the mqm group has full access to everything.
If you have set permissions using setmqaut, and done a refresh security, and you are still getting 2035s back, then you have not set all of the correct permissions.
There is nothing particular about rfhutil that is different than another client app.
This is not a problem with setmqaut, this is not a problem with rfhutil. This is simply and specifically a problem with the permissions you have granted.
I will not repeat information that is in answers to all of the many other times that "Why do I get a 2035" has been asked here.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Aug 17, 2005 6:44 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| basha wrote: |
With all repect,
Jeff, I think it doesnot seem to be working. I trieed that with my colleague. I added him into a group called TEST and had setmqaut with +all / +alladm permissions and tested with RFHUTILC. The error: Not authorized shows up. But it seems to work when I add him to mqm group. Am I missing some thing here ? |
All of resources did you set the permissions? For example when you forget the +connect for the qmgr you can simply get 2035. That's why I switch on the authority event on the qmgrs, then I can browse the events for the real answer  .
Tibor |
|
| Back to top |
|
|
|
|
