ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexIBM MQ API SupportDetermining whether a queue manager is "connectable"

Post new topicReply to topic
Determining whether a queue manager is "connectable" View previous topic :: View next topic
Author Message
e_devere
PostPosted: Wed Dec 05, 2001 10:12 am Post subject: Reply with quote

Newbie

Joined: 04 Dec 2001
Posts: 2

In the description of the QMgrName parameter for the MQCONN call, the following statement appears: "The name specified must be the name of a connectable queue manager."

How does one determine beforehand whether or not a queue manager is "connectable"?

The application that's attempting to connect to a queue manager is running on top of an MQSeries Client, using a TCP channel. The queue manager is on a server platform that may or may not be "up". If server is not up, application hangs, and this is not accept- able.

Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Wed Dec 05, 2001 12:23 pm Post subject: Reply with quote

Jedi Council

Joined: 15 May 2001
Posts: 7400

Connectable implies that the QM is started and in good health.

An application must accept the fact that the possability exists that the MQCONN call will fail, and code an approriate error routine (i.e. try again in a minute, immediatly try QM #2, etc)



_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
e_devere
PostPosted: Wed Dec 05, 2001 3:02 pm Post subject: Reply with quote

Newbie

Joined: 04 Dec 2001
Posts: 2

Thanks for your reply. I tried to be concise
when submitting my question and ended up being vague.

I AM prepared to accept the fact that MQCONN
might fail, but I'm not prepared to wait one
minute or more to find out (that's how long
it takes for MQCONN to return from a failed
attempt to connect.)

I was looking for a C function analogous to
the UNIX "ping" command that would tell me in
less than a second that a queue manager was
unreachable.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Dec 06, 2001 10:29 am Post subject: Reply with quote

Jedi Council

Joined: 15 May 2001
Posts: 7400

Hmm, you got me on this one. I have always immediatly gotten my MQCONN response, good or bad. Never had an app wait so long to find out. Maybe someone else knows/

_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
kolban
PostPosted: Fri Dec 07, 2001 10:52 pm Post subject: Reply with quote

Grand Master

Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA

I am very surprised that an MQCONN does not immediately return if the queue manager is not available. The only circumstance I could see this happening is if the machine hosting the queue manager is not running and hence a request to form the underlying TCP connection has no choice but to time out.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexIBM MQ API SupportDetermining whether a queue manager is "connectable"
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.