o have to create a
> server connection channel and a listener for the Queue Manager.
>
> I read the "MQ System Administration document" and as per the document i
> should be using,
>
> runmqlsr -t tcp -p 1441 -m QmgrName
>
> .. assuming i want a tcp type communication an
l,
>
> I am trying to automate the process of creating a QueueManager and
> configuring it the way we want. In the process i also have to create a
> server connection channel and a listener for the Queue Manager.
>
> I read the "MQ System Administration document"
You can issue the word "start" infront, as in:
start runmqlsr -t tcp -p 1441 -m QMgrName
Which will start the listener in another popup window. However, if you
logoff, this popup windows will get closed, as will the listener. You need
to either use the MMC snapin to create a listen
t i
should be using,
runmqlsr -t tcp -p 1441 -m QmgrName
.. assuming i want a tcp type communication and i want the Queue Manager to
listen at 1441. When i execute the above command (windows 2000 machine) at
the DOS prompt the control never comes back to me. Its as if i have started
a front end listen
MAIL PROTECTED] cc
N.AC.AT>
Subject
RUNMQLSR : What happens...
10/08/2004 21:42
Please respond to
Tony Boggis
...to establ
...to established connections when a runmqlsr process is terminated? I
don't have easy access to a running environment at the moment so I am
posing this question. If I have a cluster of queue managers with
active CLUSSDR/CLUSRCVR channels, what happens to those channels if the
runmqlsr proce
D] cc:
BUSA.COM> Subject: runmqlsr - 5 instances
running ?
Sent by:
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
06/22/2004 07:48
Depending on the platform what you may be seeing is all the active threads
in the one listener process (with I think three active connections in this
case). Do the PPID values all go back to the same runmqlsr process? If so
then that would suggest that this is the case.
What release of MQ is
Hi,
I'm replacing amqcrsta with runmqlsr. According to the insight I got from
the Vegas conference, and a FAQ from IBM: "..., a SINGLE listener can now
handle an unbounded number of connections..." However, whenever I start
runmqlsr, a "ps -aef | grep runmqlsr" shows fiv
eries List [mailto:[EMAIL PROTECTED] On Behalf Of Mark
D. Hansen
Sent: Tuesday, March 30, 2004 8:24 AM
To: [EMAIL PROTECTED]
Subject: Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
Thanks. Out of curiosity, why does Windows have this separate set of
amqmdain commands? What does am
> To: [EMAIL PROTECTED]
> Subject: Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
>
>
> Hi Mark,
>
> I don't know the difference between these two (I believe they
> are the same
> except the parameters may be different) but you have to run
> the runmqls
Sent: Monday, March 29, 2004 7:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
>
>
> Gidday Mark,
>
> Just curious why are you deleting and recreating the queue manager?
>
> Regards
> Tim A
>
> -O
Hi Mark,
I don't know the difference between these two (I believe they are the same
except the parameters may be different) but you have to run the runmqlsr in
another window by issuing START runmqlsr -t TCP -m xxx.
On the other hand, you can use amqmdain to start the qmgr through MQ
ser
Gidday Mark,
Just curious why are you deleting and recreating the queue manager?
Regards
Tim A
-Original Message-
From: Mark D. Hansen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30 March 2004 10:44 AM
To: [EMAIL PROTECTED]
Subject: runmqlsr vs. MQSC "START LISTENER" on Window
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Mark D.
Hansen
Sent: Tuesday, March 30, 2004 1:44 AM
To: [EMAIL PROTECTED]
Subject: runmqlsr vs. MQSC "START LISTENER" on Windows ??
Can anyone tell me the difference between using "ru
Can anyone tell me the difference between using "runmqlsr" and the MSQC "START
LISTENER" command on Windows?
I'm having trouble with runmqlsr hanging when used in the following batch file to
setup my QM ...
endmqm -w QM_eai_client
endmqlsr -w -m QM_eai_client
dltmq
That was Korn-ie!!
From: "David C. Partridge" <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: runmqlsr -i vs BlockIP
Date: Fri, 20 Feb 2004 15:46:14 -
So we get "perl"s of wisdom :-)
-Original Message-
EMAIL PROTECTED]Subject: Re:
runmqlsr
That's not strictly true. You can set the Port number in qm.ini using
the following:
TCP:
Port=14141
or
whatever. You just have to remember that this changes the default port number
of channel connection attempts so you have to specif
nnels.
Regards
John
Scott
IBM
Certified Specialist - MQSeries
Argos
Ltd
-Original Message-From: Meekin, Paul
[mailto:[EMAIL PROTECTED] Sent: 20 February 2004
10:04To: [EMAIL PROTECTED]Subject: Re:
runmqlsr
Another option is to issue the START LISTENER command from runmqsc etc.,
although thi
.
- Original Message -
From:
Meekin, Paul
To: [EMAIL PROTECTED]
Sent: Friday, February 20, 2004 10:03
AM
Subject: Re: runmqlsr
Another option is to issue the START LISTENER command from runmqsc
etc., although this has the limitation that listeners can only use the
default port
So we get "perl"s of wisdom :-)
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt,
T. Rob
Sent: 20 February 2004 14:01
To: [EMAIL PROTECTED]
Subject: Re: runmqlsr -i vs BlockIP
I'm actually a very clever script.
Instructions for managing yo
I'm actually a very clever script.
-Original Message-
From: Chan, Ian M [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:51 AM
To: [EMAIL PROTECTED]
Subject: Re: runmqlsr -i vs BlockIP
Ah! I misunderstood from the descriptionso the BlockIP exit is still
required.
BT
[mailto:[EMAIL PROTECTED]Sent: 19 February 2004
19:46To: [EMAIL PROTECTED]Subject:
runmqlsr
On AIX, is there some setting to make runmqlsr
start with the queue manager (in the same way that the channel initiator
does), or does it need to be started with it via a startup script? Had
,
T. Rob
Sent: Friday, 20 February 2004 3:12 PM
To: [EMAIL PROTECTED]
Subject: Re: runmqlsr -i vs BlockIP
Ian,
The -i parameter lets you bind the listener to a specific IP address on the
server, not a specific IP address of the remote node. This is similar to
the LOCLADDR parameter on a channel
Ian,
The -i parameter lets you bind the listener to a specific IP address on the
server, not a specific IP address of the remote node. This is similar to
the LOCLADDR parameter on a channel definition. BlockIP is completely
different and neither the runmqlsr -i parameter nor the LOCLADDR
Hi,
With the new parameter -i which can specify the IP address to listen on, is
it enough to replace the BlockIP exit program? I know BlockIP offers more
including multiple IP addresses and filter userids, however, I think the new
parameter together with the MCAUSER should be enough for internal M
Set up the listener to run from inetd. You will need
to have root authority to set this up initially. I copied the below
information from the Quick Beginnings Manual for 5.2. You will not see runmqlsr
as a running process but should see amqcrsta running.
http://www-306.ibm.com
Title: Message
Add the runmqlsr
command after the strmqm command in the startup script. The other option is to
not use the listener and set up INETD to listen on that
port.
-Original Message-From: Darren Douch
[mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 1:46
PMTo
On AIX, is there some setting to make runmqlsr
start with the queue manager (in the same way that the channel initiator does),
or does it need to be started with it via a startup script? Had a look
through the manuals and haven't found anything.
Thanks again.
Darren.
AIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: SWOT Analysis with listeners as inetd or runmqlsr AND channel
s as threads or processes
Date: Mon, 17 Mar 2003 14:11:11 -
I've experienced a couple of problems with inetd on
I've experienced a couple of problems with inetd on AIX. As a result we've
switched over to using runmqlsr. It did have some memory leaks but since
CSD04/05 it works fine.
I particularly found problems if you attempted to stop a queue manager when
using inetd. Inetd would still accep
I have heard that the RUNMQLSR has been much improved for 5.3 so it is
SUPPOSEDLY as good asd INETD over 500 connections. This statement is not
from experience or anyone else who has experience with it.
bobbee
From: Tim Armstrong <[EMAIL PROTECTED]>
Inetd for more than a couple of hundred connections is usually more
reliable. Runmqlsr and threads uses less resources. As for your second
question its determined by which type of listener you use. To quote from
the manual.
You can use inetd or the Run Listener (RUNMQLSR) command to define a TCP
MQSeries Experts,
I am inquiring from the
vast array of knowledge within the MQSeries community on two simple topics.
Please respond to the strengths and weaknesses of the following.
1)
Choice of listener:
inetd or runmqlsr process.
2)
Choice of channel:
start as a
>Paul,
>Does this (channel pools) also apply to the other 5.3 distributed
platforms?
>Dave
Yes, it applies to all 5.3 distributed platforms (not z/OS clearly).
Cheers,
P.
Paul G Clarke
WebSphere MQ Development
IBM Hursley
Instructions for managing your mailing list subscription are provided i
Paul,
Does this (channel pools) also apply to the other 5.3 distributed platforms?
Dave
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Subject: Re: Old School RUNMQLSR
>I've always started my MQ listeners (on Windows) via the command prompt -
mainly b/c I learned on version 5.0. I recently upgraded this W2K machine
to WMQ 5.3 and I continue to start
>the listeners this way - however, I'm noticing something
>I've always started my MQ listeners (on Windows) via the command prompt -
mainly b/c I learned on version 5.0. I recently upgraded this W2K machine
to WMQ 5.3 and I continue to start
>the listeners this way - however, I'm noticing something different now.
With previous versions, the listener windo
TED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
01/16/2003 08:44 AM
Please respond to MQSeries List
To: [EMAIL PROTECTED]
cc:
Subject: Re: Old School RUNMQLSR
You do get 'channel started' messages in the W2K event log..
You do get 'channel started' messages in the W2K event log..
From: Mike Davidson <[EMAIL PROTECTED]> on 01/16/2003 08:14 AM
Please respond to MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Old School RUNMQLSR
I've always started my MQ
I've always started my MQ listeners (on Windows) via the command prompt - mainly b/c I learned on version 5.0. I recently upgraded this W2K machine to WMQ 5.3 and I continue to start the listeners this way - however, I'm noticing something different now. With previous versions, the listener window
cc:
Sent by: MQSeriesSubject: Re: AIX runmqlsr problem
List
09/04/2002 07:16
PM
Please respond to
Erik:
Just in case you did not do it already: check with netstat -a if anybody is already
listening on this port.
Pavel
Erik Klemetti
cc:
Sent by: MQSeriesSubject: AIX runmqlsr problem
Erik,
It seems that your MQ listener either might be done via inetd or not
"installed" at all. If the inetd method is used, you will not see an entry
on the machine's process list (i.e. "ps" command and the "runmqlsr" process).
Take a look at your /etc/i
se it when I type ps -ef | grep runmqlsr.
It seems to be the FMCQM listner but I can't se on which port..
Utterly confused..
Please advice
Erik
>From: Warren <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: AIX runmq
inny thing that I have forgotten.
>
>I have the same config in my testing environment and the everything runs
>just fine.
>
>Env.
>AIX, MQS 5.2, DB2 7.2, WMQSI2.1, WF3.3.2
>I trying to start the listner for the WF.
>
> runmqlsr -t tcp -p 5010 -m FMCQM &
>
>a
.
HTH,
Stefan
>From: Erik Klemetti <[EMAIL PROTECTED]>
>Reply-To: MQSeries List <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: AIX runmqlsr problem
>Date: Wed, 4 Sep 2002 22:01:11 +
>
>Hi all,
>
>I have a problem with starting a listner and can't fi
r the WF.
runmqlsr -t tcp -p 5010 -m FMCQM &
and after a while it comes back with..
AMQ9218: The TCP/IP listener program could not bind to port number 5010.
I have tried to find out where it goes wrong but haven't found anything.
If anyone could give me aatleast a hint in the rigt
48 matches
Mail list logo
