| Author |
Message
|
| Garth |
 Posted: Sun Sep 22, 2002 11:20 pm Post subject: Is Q manager running or not |
 |
|
Newbie
Joined: 22 Sep 2002
Posts: 2
|
Mq series 5.2 on windows 2000 server . created a queue manger using MQ explorer . Initially Q manger connected ok as displayed on MQ Explore but later status was not connected , on trying to connect following message is observed :
' Queue manger not available for connection . Ensure that the Queue manger is running . '
This a bit confusing because the Mq Explorer display is showing the Q manger as running .
Has anyone encountered this situation before .?
nb attempting to issue the command runmqsc indicates that there is no Q manger present . |
|
| Back to top |
|
 |
| Shep |
| Posted: Mon Sep 23, 2002 1:03 pm Post subject: |
|
|
Newbie
Joined: 21 Jun 2002
Posts: 6
Location: Massachusetts
|
I have the same exact problem. I sign onto the server, start the queue manager, and everything looks fine. However, when I try to access the Queue Manager remotely from my development machine running the MQSeries client, I get the same "not available for connection" message.
I suspect this is due to the Queue Manager being started under a session associated with my userID on the Win2K server. I don't know how to get the Queue Manager running at a "service" level / system level on the Win2K server.
Any help would be appreciated. Thx in advance! |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Sep 24, 2002 9:23 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
did you copy the channel table of your Mqseries server to your machine running the mqseries client?
-Laze |
|
| Back to top |
|
|
| Nimrod |
| Posted: Wed Sep 25, 2002 5:08 am Post subject: Common prob |
|
|
Newbie
Joined: 08 Jul 2002
Posts: 6
Location: Israel
|
The message "QueueManager not available for connection..." (MQRC2059) is the most common message you could get trying to connect to a QM.
There are a few options:
- if you're working localy (that is, trying to connect to a queue manager on the same machine you're working on), either the queue manager is down, or maybe you're working through a client channel even though your on the same comp.
- if you're working with a client channel, check your MQSERVER definition.
This message when working on client simply means you can't get through to the QM, it doens't necessarily means it's down. It could be, for example, a communications failure.
the easiest way of checking this is through a simple test:
define a server-connection channel named CLIENT or something of a sort.
define a local queue, for example LOCAL.
enter a command line and type: "SET MQSERVER=LOCAL/TCP/ipaddr(port)"
ipaddr - ip address of computer running the QM
port - port the listener is running on, you can check this by getting into MQSeries Services (through the start menu), clicking the properties of the listener, and in the "parameters" tab the port number is written. This value has a default of 1414.
now type "amqsputc TEST". this should work. if it doesnt, either the listener is down, or communications is down (easily checked through ping and "telnet <ipaddr> <portnum>") or something's screwed with the QM.
the last option I can think of, is getting into the file c:\mqseries\conv\table\ccsid.tbl. In the end of the file, remove the "#" character from the two lines with "default" in the begging and restart the QM.
If all this doesn't work, I donno...
_________________
Nimrod Oren
Integration Solutions Expert,
Multiconn, Israel. |
|
| Back to top |
|
|
| 2189 |
| Posted: Thu Oct 24, 2002 6:05 am Post subject: |
|
|
Apprentice
Joined: 22 Oct 2002
Posts: 31
|
Are you connecting to the Server using Terminal services cos MQ ain't supported using Terminal Services. MQ Explorer and dspmq will say the qmgr ain't running when it is.
Instead you have to connect using Telnet or a Remote command server session. Ironically, you can connect to a server using Terminal services and then telnet to another server and it will work.
I don't believe IBM are making any attempt to fix this.
_________________
2189 errors make me  |
|
| Back to top |
|
|
| clindsey |
| Posted: Thu Oct 24, 2002 6:30 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
At last years MQ Conference, I heard that the technical issues with Terminal Services had already been solved in 5.3. There was still testing to do before any official announcements would be made. So, we may see it supported in 5.3
Charlie |
|
| Back to top |
|
|
| eeeeej |
| Posted: Wed Jun 25, 2003 5:43 am Post subject: |
|
|
Newbie
Joined: 06 Nov 2002
Posts: 4
|
Thank You!!!
I've been using this web site for 1-2 years & it has provided a lot of help. This last thread was yet 1 more example (I just wish I would have used it a couple of hours ago...)
-ej |
|
| Back to top |
|
|
|
|
