| Author |
Message
|
| ManiA |
 Posted: Fri Mar 17, 2006 9:07 am Post subject: MQAuth differences when using amqsgetc and RfhutilcReadQ |
 |
|
Newbie
Joined: 25 Jan 2006
Posts: 8
|
Hello,
WMQ 6.0.1(server and client) on PC
WMQ 5.3.11 on MQServerQMgr being accessed remotely.
MQServer(with a exclusively defined SVRCONN) is defined on the PC
The amqsputc and amqsgetc work fine directly from the command line.
Using the same MQServer parameters from the drop-down list in Rfhutilc a ReadQ reports a 2035. Just to make sure it is not RFHUtilc related, replaced(within rfhutilc) the special SVRCONN with SYSTEM.DEF.SVRCONN and got successful BrowseQ and ReadQs all the way to a 2033.
Prior to using the MQServer, used the CHLTab file with same results.
What MQAuth setups and/or config steps could I be missing?
I'm continuing to dig thru the ih03.pdf for any special requirements.
Any pointers?
Thanks.
Mani |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri Mar 17, 2006 9:12 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Is your "first" svrconn defined with a mcauserid? rfhutil might be trying to open the queue with some options that amqsputc/getc isn't (like set context).
Do you have access to the server? If so, you can turn on authority events to actually see what user is getting bounced and what the open options were....
_________________
-wayne |
|
| Back to top |
|
|
| ManiA |
| Posted: Fri Mar 17, 2006 9:34 am Post subject: |
|
|
Newbie
Joined: 25 Jan 2006
Posts: 8
|
Wayne,
Yes, the first SVRCONN is setup with a MCAUSER and the Qs I'm accessing have been setup with the required AUTHs.
Yes, I do have access to the server and I will try your suggestion.
Thanks.
Mani |
|
| Back to top |
|
|
| ManiA |
| Posted: Fri Mar 17, 2006 11:41 am Post subject: |
|
|
Newbie
Joined: 25 Jan 2006
Posts: 8
|
Hi Wayne,
Found out from the error logs the Auth failure was happening at a "inq".
For this test I was using AliasQs. With the baseQL's Auths unchanged, adding a "allow inq" for the GETQAlias made Rfhutilc read the Q. However, the amqsgetc against the same GETQAlias was able to get msgs prior to this action.
The conclusion I come to is - rfhutilc does an "inq" and then a "get". Is that a right conclusion? Maybe you can explain this behavior better than I've understood.
Thanks.
Mani |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Mar 17, 2006 11:47 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
The conclusion I come to is - rfhutilc does an "inq" and then a "get". Is that a right conclusion? Maybe you can explain this behavior better than I've understood.
|
apparently so..where-as amqsput/getc doesn't ....
so now everything is ok, yes?
_________________
-wayne |
|
| Back to top |
|
|
| ManiA |
| Posted: Fri Mar 17, 2006 12:10 pm Post subject: |
|
|
Newbie
Joined: 25 Jan 2006
Posts: 8
|
Yes, with the INQ authority added for the GETQAlias, Rfhutilc is working fine.
Thank you for your help!
Mani |
|
| Back to top |
|
|
|
|
