| Author |
Message
|
| dp111443 |
 Posted: Wed Nov 09, 2005 12:56 am Post subject: Broker deploy errors |
 |
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
I've checked similar forums related to this problem with no solution to the problem.
The error I am getting is from the configuration Manager when deploying to
an Intel Linux Broker (RHEL 3) which uses Broker version 5 CSD04, MQ 5.3
CSD07, DB2 8.1.7 CSD06.
I can deploy flows and stop and start them however always get the following
error after the successful responses:
BIP1536S: Configuration Manager unable to register for internal
subscriptions with broker TESTBK.
Although the preceding deploy operation was successful, a subsequent
attempt by the Configuration Manager to register for internal subscriptions
with broker TESTBK was not successful. This means that the Message Brokers
Toolkit may not reliably show the correct status of the resources assigned
to broker TESTBK. The Configuration Manager also writes this message to the
system event log, accompanied by other messages giving details of the
problem.
Look at the messages for this problem in the system event log. Determine
and correct the cause of the problem before attempting to deploy to this
broker again. If this problem persists, contact your IBM support center.
On the broker itself I get the following errors:
Nov  7 17:42:59 gblabl10 MQSIv500[31042]:
(GBSCC01D.EXEC_TEST)[376856]BIP4041E:Execution group 'EXEC_TEST' received
an invalid configuration message. See the following messages for details of
the error. : GBSCC01D.1b359047-0701-0000-0080-c2bcd066ddbb:
build/S500_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 364:
ImbConfigurationNode::evaluate: ComIbmConfigurationNode: ConfigurationNode
Nov  7 17:42:59 gblabl10 MQSIv500[31042]:
(GBSCC01D.EXEC_TEST)[376856]BIP2230E: Error detected whilst processing a
message in node 'DynamicSubscriptionEngine'.:
GBSCC01D.1b359047-0701-0000-0080-c2bcd066ddbb:
/build/S500_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubResource.cpp:
1359: ImbPubSubResource::handleResource: DynamicSubscriptionEngine:
DynamicSubscriptionEngine Nov  7 17:42:59 gblabl10 MQSIv500[31042]:
(GBSCC01D.EXEC_TEST)[376856]BIP7150E: User id 'WMQIBM' not authorized to
put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'GBAHES48' using
accounting token
'0000000000000000000000000000000000000000000000000000000000000000'. :
GBSCC01D.1b359047-0701-0000-0080-c2bcd066ddbb:
/build/S500_P/src/DataFlowEngine/JavaNodeLibrary/ImbPubSubSubscribeMessageHandler.cpp:
524: ImbPubSubSubscribeMessageHandler::checkQueueAuthority:
ComIbmPSControlNode: ControlNode
The configuration manager user id is 'WMQIBM' and the userid of the broker
on Intel Linux is 'wmqibm'. Â The fact that I can deploy flows, stop and
start flows, etc. suggests to me that the authority is ok, however this
error suggests a problem somewhere.
The 'wmqibm' userid is also part of the mqm group on the Linux machine.
I have checked the authorities on the queue managers and queues on both ends (config mgr and broker) which both have mqm rights.
Appreciate some help with this problem
thanks and regards....
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Wed Nov 09, 2005 1:19 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| Quote: |
(GBSCC01D.EXEC_TEST)[376856]BIP7150E: User id 'WMQIBM' not authorized to
put to queue 'SYSTEM.BROKER.ADMIN.REPLY' on queue manager 'GBAHES48' |
fix that first. WMQIBM is not eq wmqibm
_________________
Regards, Butcher |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed Nov 09, 2005 1:42 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi dp111443(weird selection of name),
As Butcher said u got to fix your authority....
When ur using MB, login with the user who has the authority.....if u try to start the broker with a user who does not have access, a message to start the Broker will be stored on the System Queue, and the start will fail..... and later even if you login with the correct suer ur message will lie 2nd to the first message and hence still not start the Broker.....
Therefore, work with the correct user always.
Regards. |
|
| Back to top |
|
|
| dp111443 |
| Posted: Wed Nov 09, 2005 1:48 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
is that what we are saying then....that the configuration manager Userid cannot be different case to the broker useid even though they are named the same?
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| dp111443 |
| Posted: Wed Nov 09, 2005 1:53 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi Butcher,
Thanks for your response.
The broker userid 'wmqibm' is a part of of the mqbrks and mqm group and can start and stop the broker no problem....theres no issue there
The config mgr is also able to register the broker, create a new exec group and deploy flows successfully. I have even put messages through the broker to prove they are working.
This is why I don't think its an authority issue even though it suggest that.
Finally, the 'wmqibm' user (broker) & 'WMQIBM' (configmgr) both have full MQ rights. Ive checked the authorites using dspmqaut
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed Nov 09, 2005 3:11 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi dp111443,
I think the problem is that ur user WMQIBM(config mgr) does not have authority to put messages to Boker QM with user wmqibm....
I think u might be able to fix the problem by creating a local user WMQIBM on ur broker system and giving him authority.....or give the remote WMQIBM user the authority....
Try it out, dont know if it works....
Regards. |
|
| Back to top |
|
|
| dp111443 |
| Posted: Wed Nov 09, 2005 5:37 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi,
Unfortunately that is the problem....I cannot create another user called WMQIBM when I've already got a user created called wqmibm on the broker.
the same applies on the windows congig mgr.
cheers
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Nov 09, 2005 7:45 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Let me see if I understand:
You have a configmgr on windows, userid: WMQIBM,
on the linux system, a broker, userid wmqibm.
On the linux system, both userids are in the "mqm" group.
(or are you saying that on the linux system you only have a wmqibm userid and you can't create a WMQIBM userid?)
EDIT: just as an aside, even if your userid is UPPERCASE in windows, MQ will automatically fold it to a lowercase userid (unless you have your own Message exit) when you go to a UNIX platform.
_________________
-wayne |
|
| Back to top |
|
|
| dp111443 |
| Posted: Thu Nov 10, 2005 12:10 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
| Quote: |
yes thats right. I have one userid on the broker system 'wmqibm' which is part of the mqm and the broker group. But I cannot create another userid called WMQIBM as linux won't allow it (says the system administrators)
I think the problem here is that the windows USERID WMQIBM isn't allowed to put to the linux queue manager SYSTEM.BROKER.ADMIN.REPLY.
The two options I've got here is:
change the windows id to lowercase
or change the linux one to uppercase.
Can't do either as - windows config mgr already manages mainframe brokers and because of RACF, the userid of the config mgr has to be uppercase. And option 2, can't be done either says the linux admins as they have tried but failed.
So the only option I can see here is have a different config manager pc for distributed brokers and leave the current one for mainframe.
thanks, |
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 10, 2005 2:32 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
From the manual:
| Quote: |
User IDs across systems
Platforms other than Windows systems and UNIX systems use uppercase characters for user IDs. To allow Windows systems and UNIX systems to use lowercase user IDs, the following conversions are carried out by the message channel agent (MCA) on these platforms:
At the sending end
The alpha characters in all user IDs are converted to uppercase, if there is no message exit installed.
At the receiving end
The alpha characters in all user IDs are converted to lowercase, if there is no message exit installed.
Note that the automatic conversions are not carried out if you provide a message exit on UNIX systems and Windows systems for any other reason. |
This means two things: when WMQIBM is send to the mainframe from windows, it is always automatically uppercased by MQ, and when that userid is received by linux, it is in lowercase.
Unless, you have message exits. Do you have message exits on your channel from windows to linux?
(and, btw, I have wschutz and WSCHUTZ here on my linux machine)
_________________
-wayne |
|
| Back to top |
|
|
| dp111443 |
| Posted: Thu Nov 10, 2005 3:06 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi wschutz,
We don't have any message exits in between. We are using straight sender to reciever channel pairs.
so I don't beleive that MQ is changing the case as you suggest otherwise it wouldn't be throwing that error.
| Quote: |
(and, btw, I have wschutz and WSCHUTZ here on my linux machine)
|
Can you tell me how you created these ID's on the linux machine, so I've got some fire power to throw back to my linux admin guys.
thanks,
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 10, 2005 3:17 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| Can you tell me how you created these ID's on the linux machine, so I've got some fire power to throw back to my linux admin guys. |
Thats trivial:
| Code: |
| /usr/sbin/adduser WSCHUTZ |
Can you do a test? Can you send a message from WMQIBM on the wondows machine to SYSTEM.DEFAULT.LOCAL.QUEUE on the linux machine and confirm that the userid isn't converted to lowercase?
I just tried this yesterday from my windows machine where I defined a usr "UPPERC" and sent a message into linux. Without message exits, the userid showed up as "upperc". With a message exit in place, it remained "UPPERC".
We should really understand why this isn't happening on your machine and try to fix that.
As an aside, what versions of MQ (and CSDs) are on windows & linux?
_________________
-wayne |
|
| Back to top |
|
|
| dp111443 |
| Posted: Thu Nov 10, 2005 7:11 am Post subject: |
|
|
Voyager
Joined: 25 Feb 2004
Posts: 82
|
Hi,
Pardon my ignorance here...
How do I send an uppercase message from windows to the queue SYSTEM.DEFAULT.LOCAL.QUEUE on linux when this is a local queue on the the windows machine.
Windows MQ 5.3 CSD05
Linux MQ 5.3 CSD09
Finally, with regards to adding the userid on unix:
[/quote]
/usr/sbin/adduser WSCHUTZ
| Quote: |
We get:
[root@hostname root]# /usr/sbin/adduser DPTEST
adduser: invalid user name 'DPTEST' |
_________________
Integration Design/Developer
IBM Certified System Administrator -
WebSphere MQ V5.3 |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 10, 2005 7:19 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
Posted: Thu Nov 10, 2005 10:11 am Post subject:
--------------------------------------------------------------------------------
Hi,
Pardon my ignorance here...
How do I send an uppercase message from windows to the queue SYSTEM.DEFAULT.LOCAL.QUEUE on linux when this is a local queue on the the windows machine.
EDIT: Define a qremote on the windows machine (call it MYTEST) with an rname(SYSTEM.DEFAULT.LOCAL.QUEUE) and a rqmname(linux-qmgr). The use amqsput MYTEST to put a message to the queue.
|
No, I didn't mean an uppercase message. I meant send a message from your uppercase userid on windows (ie WMQIBM) to the linux machine and then use amqsbcg to display the userid in the message descriptor. It SHOULD be in lowercase.
Re uppercase userids, see: (scroll toward the bottom to see the responses to the question)
http://64.233.161.104/search?q=cache:PP5f6ot6mOUJ:www.experts-exchange.com/Operating_Systems/Q_21295540.html+%22adduser:+invalid+user+name+%22+uppercase&hl=en
_________________
-wayne |
|
| Back to top |
|
|
|
|
