MQSeries.net :: View topic - Alias queue to resolve problems with authorizatons....

My_Quest · Posted: Thu Aug 25, 2005 6:34 am Post subject:

Dear All,
one of our developer on "z" side ,can connect to the Queue manager(on Z side) just fine (as verified with another tool called "MQ Visual Edit") -- but when he goes to open XX.XXTRN.INPUT.QUEUE(its a remote queue), it fails with the 2035 error msg.

According to his docs, this is:

2035 (X'07F3') MQRC_NOT_AUTHORIZED
Explanation: The user is not authorized to perform
the operation attempted:
v On an MQOPEN or MQPUT1 call, the user is not
authorized to open the object for the option(s)
specified.

(edited for brevity).

The developer on "Y" side(our end) had the same problems at first, until he realized that he was trying to open the queue with "MQC.MQOO_INPUT_AS_Q_DEF + MQC.MQOO_OUTPUT as parameters, that is, trying with READ AND WRITE. It seems like remote queues ONLY want to be written to (which xx.xxTRN.INPUT.QUEUE is), and not read, so once he changed it to just MQC.MQOO_OUTPUT I could connect just fine.(this was discussed in this forum and got an satisfactory answer :- ....)

So the developer on our side(Y side) suggested this:

The problem is that "Z" side developer DOES NOT HAVE ANY CONTROL over how Cache (his app server) connects to an MQ server. it would appear that it is asking for read, getting denied, and failing. To debug this, it would be extremely helpful to allow both read AND write to xx.xxTRN.INPUT.QUEUE, and see if the problem goes away. Can you do this for him?

But folks to give authorizations on remote queue, the "Z" side developer have no idea under which "user id" he is connecting the QMGR.Using setmqaut and giving allmqi to an remote queue will help? or I am thinking of creating an Alias queue which targets to the remote queue where I can enable both put & get on alias queue...does this solve my problem or is there any other way for it?

Thanks in advance...