| Author |
Message
|
| dexter |
 Posted: Fri Jan 07, 2011 1:10 pm Post subject: Unable to start SYSTEM channels |
 |
|
Apprentice
Joined: 07 Jan 2011
Posts: 32
Location: Michigan, USA
|
MQ v7.0.1, WMB 7.0, zLinux v11
I have a broker and its queue manager on my zLinux box. I am unable to connect to the broker's queue manager from MQ Explorer using the SYSTEM.ADMIN.SVRCONN channel. I also tried connecting to the broker from the Broker Explorer interface using the SYSTEM.BKR.CONFIG channel. Didn't work out either.
After some investigation, I found that the SYSTEM.ADMIN.SVRCONN channel was not created. I created it, but now it doesn't start. I checked the listener. It's running. I restarted the queue manager. Nothing makes the channel start up.
Also, none of the channels are listed as running. DIS CHS(*) brings up no results. Even the SYSTEM. BKR.CONFIG channel is down along with the other channels.
I'm sure I'm missing something fairly obvious here. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Jan 07, 2011 1:22 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Didn't work out either |
And by this you mean that you received a ReasonCode or something else?
You don't start SVRCONN channels. They start when an inbound flow arrives.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| dexter |
| Posted: Fri Jan 07, 2011 1:37 pm Post subject: |
|
|
Apprentice
Joined: 07 Jan 2011
Posts: 32
Location: Michigan, USA
|
Ok. So, the channel is supposed to start up automatically when I try to connect to the queue manager or broker on MQ Explorer. Understood.
Here's the Reason Code that I got when I tried to connect.
AMQ4036. Access not permitted. You are not authorized to perform this operation.
But I am a member of the mqm and mqbrkrs group. So, I shouldn't have any access issues.
You may say that on windows, when I try to connect to the queue manager, the user id that goes in is "domain/userid" and not just "userid".
But I'm able to connect to queue managers and brokers on a different zlinux box with the same setup. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 07, 2011 2:07 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
An instance of a SVRCONN will be started every time an MQCONN is made using it.
This will not cause the SVRCONN to be in a "running" state.
If you're getting an MQRC2035, not authorized, it's because the setup is NOT the same as the other machine that works. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 07, 2011 2:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dexter wrote: |
Ok. So, the channel is supposed to start up automatically when I try to connect to the queue manager or broker on MQ Explorer. Understood.
Here's the Reason Code that I got when I tried to connect.
AMQ4036. Access not permitted. You are not authorized to perform this operation.
But I am a member of the mqm and mqbrkrs group. So, I shouldn't have any access issues.
You may say that on windows, when I try to connect to the queue manager, the user id that goes in is "domain/userid" and not just "userid".
But I'm able to connect to queue managers and brokers on a different zlinux box with the same setup. |
Not necessarily the same setup. Talk to your friendly MQ admins.
A lot of the System channels are disabled by design or secured via SSL by the MQ Admins.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Jan 08, 2011 10:18 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Look at the error logs on the qmgr that you tried to connect to. What error(s) are logged there?
Look at the error logs on the platform from where you tried to connect. What error(s) are logged there?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| dexter |
| Posted: Sun Jan 09, 2011 5:27 pm Post subject: |
|
|
Apprentice
Joined: 07 Jan 2011
Posts: 32
Location: Michigan, USA
|
| No errors logged from January 2k11 in the /var/mqm/errors logs. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jan 09, 2011 5:42 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's more important to be worried if you actually see a SVRCONN in a "running" state than if you don't.
What's your actual question? |
|
| Back to top |
|
|
| dexter |
| Posted: Sun Jan 09, 2011 5:44 pm Post subject: |
|
|
Apprentice
Joined: 07 Jan 2011
Posts: 32
Location: Michigan, USA
|
My actual problem/question:
I am unable to connect to the queue manager, that resides on a zLinux box, from an MQ Explorer interface on Windows.
I get the Authorization error I mentioned in a previous post. |
|
| Back to top |
|
|
| dexter |
| Posted: Sun Jan 09, 2011 5:54 pm Post subject: |
|
|
Apprentice
Joined: 07 Jan 2011
Posts: 32
Location: Michigan, USA
|
Update:
Now I'm able to connect using the SYSTEM.BKR.CONFIG channel, when I tried to create a new broker connection from the Broker Explorer console in MQ Explorer.
But I still can't connect in a separate instance using SYSTEM. ADMIN.SVRCONN.
I don't know what I changed that let this happen because I remember trying before and being unsuccessful.
I'm not too worried though, now that I can at least connect.
Thanks everyone. |
|
| Back to top |
|
|
|
|
