Author |
Message
|
sknrt1 |
Posted: Thu Apr 29, 2004 9:27 am Post subject: error :BIP1536S & BIP7150E |
|
|
Apprentice
Joined: 22 Jan 2003 Posts: 39 Location: USA
|
Hi,
setup:)
-------
Deploying from Local configmgr to the Broker on AIX. Configmgr has been created with service id 'a4kx', but not the broker. 'a4kx' is part of the mqm, but not part of 'mqbrops' on broker box.
The Deploys goes well as the flow is being exeuted with test msg. But the control center and Broker log spits the following error, when the deploy happens:
Control Center Log:)
------------------
BIP1536S: Configuration Manager unable to register for internal subscriptions with broker MQIZB99.
Although the preceding deploy operation was successful, a subsequent attempt by the Configuration Manager to register for internal subscriptions with broker MQIZB99 was not successful. This means that the Control Center Operations view may not reliably show the correct status of the resources assigned to broker MQIZB99. The Configuration Manager also writes this message to the system event log, accompanied by other messages giving details of the problem.
Borker Log on AIX:)
------------------
Apr 29 09:56:58 roc08650d040 WMQIv210[87614]: (MQIZB99.$SYS_mqsi)[2314]BIP7150E: User id 'a4kx' not authorized to put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'MQSI_QM' using accounting token '0000000000000000000000000000000000
000000000000000000000000000000'. : MQIZB99.82A6E590-12B3-11D3-81A2-00203506A68E:
/build/S210_P/src/DataFlowEngine/ImbPubSubSubscribeMessageHandler.cpp: 261: Imb
PubSubSubscribeMessageHandler::getAttributes: ComIbmPSControlNode: ControlNode
There seems to be different suggestions made towards there errors in this forum. Here i can't have the Broker re-created with service id 'a4kx'.
And this error doesn't recommend me to have 'A4KX' upper case id to be added to AIX.
Are there any ways to avoid these errors.
Any help would be greatful.
Thanks |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Apr 29, 2004 9:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You could set an MCA on the channels between the two queue managers. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sknrt1 |
Posted: Fri Apr 30, 2004 7:43 am Post subject: |
|
|
Apprentice
Joined: 22 Jan 2003 Posts: 39 Location: USA
|
Hi Jeff,
Thanks for the response.
I did try to set the user on MCA and no use, Still facing the same error.
Question: Do i need to be part of 'mqbrops' on Broker AIX box, for deploying flows from Configmgr on my box created with my id.
At persent i am not part of it, but able to assign and deploy to the broker and don't get any authorization errors, except the one posted in this.
thanks |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Apr 30, 2004 7:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
I meant, set the MCA to some user that has the proper security for the operation you are performing, not set the MCA to the user that does not have the proper security for the operation you are performing. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
sknrt1 |
Posted: Fri Apr 30, 2004 12:23 pm Post subject: |
|
|
Apprentice
Joined: 22 Jan 2003 Posts: 39 Location: USA
|
This is solved.
Its due to not having put/get authority for the user on Transmission Queue 'MQSI_QM' on Broker QM. Did set the authority and things worked fine.
Thanks |
|
Back to top |
|
 |
bdrummond |
Posted: Thu May 06, 2004 6:47 am Post subject: |
|
|
Disciple
Joined: 06 May 2004 Posts: 164
|
sharpyk wrote: |
This is solved.
Its due to not having put/get authority for the user on Transmission Queue 'MQSI_QM' on Broker QM. Did set the authority and things worked fine.
Thanks |
I'm having this same problem and as the WMQI user does not exist on the broker machine, I thought I could get away with having the WMQI user as the MCA user id on the sender channel of the AIX broker.
However, the problem persists.
Any ideas or would it be best to create a new user on the AIX broker machine..? |
|
Back to top |
|
 |
sknrt1 |
Posted: Fri May 07, 2004 5:23 am Post subject: |
|
|
Apprentice
Joined: 22 Jan 2003 Posts: 39 Location: USA
|
Hi,
In this case, the user should be able to write to the XMITQ on the broker QM (wich is same name as ConfigMgr QM).
Try as follows:
"dspmqaut -s QMName -t queue -n XMITQname -p userid"
It should result with no access, as u were saying the user is not available on AIX.
so set the following for the user id:
""setmqaut -s QMName -t queue -n XMITQ -p userid +put +get +browse"
The user doesn't have to be part of full 'mqm' group, but should be atleast sub-level of mqm group to do the put/get.
And it should work, as Broker gets the msg having ConfigMgr's service id on it and broker uses the same id to write to the reply queue. Having set the authority for the user id, things should be fine.
setting the MCAUser doesn't work. As this error is at queue level on Broker itself.
you can post further details on this.
thanks |
|
Back to top |
|
 |
bdrummond |
Posted: Fri May 07, 2004 6:50 am Post subject: |
|
|
Disciple
Joined: 06 May 2004 Posts: 164
|
Thanks for your help on this. The problem is now solved.
Cheers. |
|
Back to top |
|
 |
Anirud |
Posted: Mon Apr 25, 2005 12:21 pm Post subject: |
|
|
 Master
Joined: 12 Feb 2004 Posts: 285 Location: Vermont
|
Hi Sharpyk,
Thanks for the information.
I had the same issue and fixed it following your instructions.
I love this site
Thanks again. |
|
Back to top |
|
 |
|