| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| rfhutilc connect to remtoe queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| amerlin |
 Posted: Mon Nov 28, 2011 3:24 am Post subject: rfhutilc connect to remtoe queue |
 |
|
Newbie
Joined: 28 Nov 2011
Posts: 4
|
Hello all;
I'm trying to connect to queue on remote computer from my computer using rfhutilc, but no luck
So, what I have so far:
ComputerA:
MQ server, with queue manager - FirstQM, queue - LocalQ1, channel - NewConnChannel, listeners - someListener running on port 3414.
with rfhutil running here is all ok - I'm able to put and read msgs.
ComputerB(my computer):
MQ client, rfhutil(c)
So I'm trying to connect to FirstQM,LocalQ1 running on ComputerA
set env variable - MQSERVER with value
NewConnChannel/TCP/COMPUTER_A_DNS_NAME(3414)
Started rfhutilc.exe
specify in the Remote Queue Manager Name text field FirstQM
and press Load Names button.
As a result I got
12.52.50 2035 Not authorized (Connect)
2035 Not authorized (Connect)
2035 Not authorized (Connect)
Error getting queue names,
So I decided to specify user id/pass of the user that was used to run/create all the things on ComputerA.
I put user id/pass in the pop-up form by pressing button set Conn Id
And still have same msgs - not authorized
Any ideas what I did wrong, what should I do or configure ?
Thank you |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Nov 28, 2011 3:33 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Using a CCDT makes rfhtuilc must easier to use, especially between different QMRs. It even shows the QMs in the CCDT as a drop-down list.
2035 means your Windows id does not have access. You can put what you like in the id field - but MQ client will pass the Windows id.
Why not enable auth events on the QM and look at the admin event record which will tell you what id was passed to MQ?
Add your id to a suitable group on the QM and set up the OAM authority entries appropriately.
What version of MQ client do you have? |
|
| Back to top |
|
|
| amerlin |
| Posted: Mon Nov 28, 2011 3:39 am Post subject: |
|
|
Newbie
Joined: 28 Nov 2011
Posts: 4
|
| Quote: |
Using a CCDT makes rfhtuilc must easier to use, especially between different QMRs. It even shows the QMs in the CCDT as a drop-down list.
|
Sorry, what is CCDT ? and how can I run/use it
| Quote: |
Why not enable auth events on the QM and look at the admin event record which will tell you what id was passed to MQ?
|
Another stupid question, how to do it ? can you give a link to apropriate doc ? or in short words where to find needed menu  ?
| Quote: |
| What version of MQ client do you have? |
Websphere MQ fix pack 7.0.1.4
Thank you for your help |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Nov 28, 2011 4:46 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I use support pac MO71 for admin, it can set auth events on, but the MQSC command is ALTER QMGR AUTHOREV(ENABLED)
Then browse queue SYSTEM.ADMIN.QMGR.EVENT for the event records - again best done with MO71, or you could use MS0P.
A CCDT is a client channel definition table - a fairly fundamental part of MQ - all documented in the usual places. I use support pac MO72 to maintain mine. |
|
| 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
|
|
|
|
