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 Index » IBM MQ Installation/Configuration Support » Starting Listeners in Windows 2000

Post new topic  Reply to topic
 Starting Listeners in Windows 2000 « View previous topic :: View next topic » 
Author Message
khookguy
PostPosted: Thu Apr 08, 2004 6:46 am    Post subject: Starting Listeners in Windows 2000 Reply with quote

Novice

Joined: 14 Jan 2002
Posts: 13

I'm running a queue manager under Windows 2000. I've defined a listener using amqmdain crtlsr. However, when I start the QM, the listener doesn't start up. I've also tried the MQSC "START LISTENER" command, which doesn't start the listener that I've defined.

This is a problem, because I'm trying to create scripts to get a bunch of QMs up and running within a cluster. But, without the listeners running, the QM cluster sender channels can't start. I can start the listeners using the MQ Services snap-in, but haven't been able to figure out how to do it using a MQSC or amqdain command.

Any ideas out there?

Thanks,

Mark
Back to top
View user's profile Send private message Send e-mail
offshore
PostPosted: Thu Apr 08, 2004 9:39 am    Post subject: Reply with quote

Master

Joined: 20 Jun 2002
Posts: 222

Mark,

I'm somewhat confused by your question for needing scripts to get the queue managers up and running.

But that aside here's what I would recommend:

1.] Create an NT CMD file (ie: start_listener.cmd)
Inside the file put the following:
runmqsc < c:\mq_scripts\listinit.mq


2.] Create a 2nd file called "listinit.mq" <file referenced above> or whatever you want to call it.
This is just a text file. Inside that file put:
sta listener



In the 1st file (before calling the runmqsc commands) you could start the queue manager with the strmqm & strmqcsv .

In the 2nd file "listinit.mq" you could any RUNMQSC commands you would like to be executed(sta listener, sta chinit, ect).


HTH
      Back to top
      View user's profile Send private message Send e-mail
      khookguy
      PostPosted: Thu Apr 08, 2004 9:50 am    Post subject: Reply with quote

      Novice

      Joined: 14 Jan 2002
      Posts: 13

      HTH,

      Thanks. I've tried this approach, but it doesn't seem to work. The MQSC command "START LISTENER" doesn't seem to start up the listener that I created with the "amqmdain crtlsr" command. I solved it by starting the queue manager with "amqmdain start" - which seems to automatically start the listener that I defined.

      In case you are wondering why I'm using "amqmdain crtlsr" to create the listener, it is because "START LISTENER" doesn't let me define the port to listen on. I need to listen on ports other than just the default 1414.

      However, I'm not happy with this solution, because I don't like using the amqmdain commands. I'd like to develop scripts that work under both Unix and Windows.

      Any other suggestions would be much appreciated.
      Back to top
      View user's profile Send private message Send e-mail
      clindsey
      PostPosted: Thu Apr 08, 2004 10:09 am    Post subject: Reply with quote

      Knight

      Joined: 12 Jul 2002
      Posts: 586
      Location: Dallas, Tx

      If you are starting a queue manager with services, amqmdain is the best method. This is not tied to the login user. It starts the qm and services as a Windows service so it survives a logoff. This is the windows way of doing nohup.

      Charlie
      Back to top
      View user's profile Send private message
      JasonE
      PostPosted: Mon Apr 26, 2004 4:28 am    Post subject: Reply with quote

      Grand Master

      Joined: 03 Nov 2003
      Posts: 1220
      Location: Hursley

      Just to add some comments to this (been away!)...

      Basically try to NEVER mix command line and GUI/amqmdain. You either want the qmgr to be under the MQ userid, surviving logoffs and monitoring its components, OR you want it to run under your userid and not survive logoffs.

      There is no way in amqmdain to start and stop a child service directly, and runmqlsr start listener does not take into account anything which is defined to the MQ services. (Be careful - runmqsc START * all start processes which run under your userid)

      So the best you can do is either
      crtmqm QM
      amqmdain crtlsr...
      amqmdain crt...
      amqmdain start QM

      or

      crtmqm
      strmqm
      start /b runmqlsr -m QM -t TCP -p 1414 etc
      and never logoff...!
      Back to top
      View user's profile Send private message
      Display posts from previous:   
      Post new topic  Reply to topic Page 1 of 1

      MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » Starting Listeners in Windows 2000
      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.