Re: RUNMQLSR
Thanks a bunch Roger. Thats the command i was looking for. It solves most of my problems. Thanks again! At 12:25 PM 9/29/2004 -0400, Roger Lacroix wrote: Hi, Download and read the WMQ System Administration manual, in particular, go to the chapter on 'amqmdain' and read the section about 'crtlsr'. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting Usha Suryadevara <[EMAIL PROTECTED]>: > Hi all, > > 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" and as per the document 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 listener process. I close the command prompt, i stop the > listener. > > I have created the listener many times before but never using a command. I > have always used the MMC snap-in to do so. What command can i use to start > the listener as a background process ? > > Thanks in advance, > Usha > > 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 > 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 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
Re: RUNMQLSR
Hi, Download and read the WMQ System Administration manual, in particular, go to the chapter on 'amqmdain' and read the section about 'crtlsr'. Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting Usha Suryadevara <[EMAIL PROTECTED]>: > Hi all, > > 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" and as per the document 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 listener process. I close the command prompt, i stop the > listener. > > I have created the listener many times before but never using a command. I > have always used the MMC snap-in to do so. What command can i use to start > the listener as a background process ? > > Thanks in advance, > Usha > > 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 > 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
Re: RUNMQLSR
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 listener, or use the amqmdain to create a listener. See Chapter 17 of the Sys Admin Guide. John Scott IBM Certified Specialist - MQSeries Argos Ltd. -Original Message- From: Usha Suryadevara [mailto:[EMAIL PROTECTED] Sent: 29 September 2004 14:35 To: [EMAIL PROTECTED] Subject: RUNMQLSR Hi all, 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" and as per the document 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 listener process. I close the command prompt, i stop the listener. I have created the listener many times before but never using a command. I have always used the MMC snap-in to do so. What command can i use to start the listener as a background process ? Thanks in advance, Usha 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 ** Check our latest prices and full range at http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and/or confidential, and is intended exclusively for the addressee. Unauthorised disclosure, copying or distribution of the contents is strictly prohibited. The views expressed may not be official policy, but the personal views of the originator. If you have received this message in error, please advise the sender by using the reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for viruses, high-risk file extensions, and inappropriate content. 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
RUNMQLSR
Hi all, 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" and as per the document 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 listener process. I close the command prompt, i stop the listener. I have created the listener many times before but never using a command. I have always used the MMC snap-in to do so. What command can i use to start the listener as a background process ? Thanks in advance, Usha 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
Re: RUNMQLSR : What happens...
Tony, Well it all depends on where the channels are running. If the channels are running as threads of the listener which was the case prior to 5.3 then the channels themselves will terminate (and probably not in a nice way if you're talking KILL -9 or task manager here). 5.3 and after, killing the listener, by default, will have no effect on your running channels because they are actually running in an AMQRMPPA process. The time it takes a remote system to detect a channel that has been killed on a remote system depends on a number of factors such as type of channel, keep alive settings, heartbeat interval, location of the two ends of the channel etc. In general it is a good idea to have keepalive switched on, a reasonable keep alive interval ie. much less than 2 hours and heatrbeat intervals that are not too long. Sorry if this sounds a little vague, Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley Tony Boggis <[EMAIL PROTECTED]> Sent by: MQSeries To List [EMAIL PROTECTED] <[EMAIL PROTECTED] cc N.AC.AT> Subject RUNMQLSR : What happens... 10/08/2004 21:42 Please respond to Tony Boggis ...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 process is terminated (in particular in a Solaris environment) on a single queue manager? How long does it ordinarily take for remote systems to spot that a connection to another cluster queue manager is unavailable (before a connection goes to retrying)? 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 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
RUNMQLSR : What happens...
...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 process is terminated (in particular in a Solaris environment) on a single queue manager? How long does it ordinarily take for remote systems to spot that a connection to another cluster queue manager is unavailable (before a connection goes to retrying)? 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
Re: runmqlsr - 5 instances running ?
Please ignore last posting, It seems to be specific to this platform( Linux/zOS). On AIX, it shows only one. "Benjamin F. Zhou"To: [EMAIL PROTECTED] <[EMAIL PROTECTED] cc: BUSA.COM> Subject: runmqlsr - 5 instances running ? Sent by: MQSeries List <[EMAIL PROTECTED] en.AC.AT> 06/22/2004 07:48 AM Please respond to MQSeries List 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 five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist Messaging&Integration Supp. Mercedes-Benz USA x.2474 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 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
Re: runmqlsr - 5 instances running ?
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 this and how are you starting the listener? If its 5.3 I'd expect one runmqlsr per QM, and on (or more) amqrmppa processes with multiple threads. David -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Benjamin F. Zhou Sent: 22 June 2004 12:49 To: [EMAIL PROTECTED] Subject: runmqlsr - 5 instances running ? 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 five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist Messaging&Integration Supp. Mercedes-Benz USA x.2474 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 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
runmqlsr - 5 instances running ?
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 five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist Messaging&Integration Supp. Mercedes-Benz USA x.2474 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
Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
Amqmdain - don't know what it stands for, but it is used to not only
start services, but to specify that they are to start automatically when
a queue manager starts, as well as starting these things under the MQ
userid, and other things.
Peter Heggie
-Original Message-
From: MQSeries 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 amqdain stand for??
Thanks,
Mark
> -Original Message-
> From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Chan,
> Ian M
> Sent: Monday, March 29, 2004 8:07 PM
> 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 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
> services. Look at the System Admin Guide Chapter 17 for the
> detail command
> syntax.
>
> Cheeers,
>
> Ian
>
> -Original Message-
> From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf
> Of Mark D.
> Hansen
> Sent: Tuesday, 30 March 2004 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: runmqlsr vs. MQSC "START LISTENER" on Windows ??
>
>
> 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
> dltmqm QM_eai_client
> crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q
> QM_eai_client
> runmqlsr -t tcp -m QM_eai_client -p 1414
> strmqm QM_eai_client
> strmqcsv QM_eai_client
> runmqsc QM_eai_client
> And here is the file "client.mqsc" ...
>
> ** MSQC commands to set up the Client
> ** Make the QMGR a Cluster Repository
> ALTER QMGR REPOS(EAI)
> ** Join the EAI cluster
> DEFINE CHANNEL(TO.EAI_CLIENT) +
> CHLTYPE(CLUSRCVR) TRPTYPE(TCP) +
> CONNAME('eai-client2.javector.com') CLUSTER(EAI) +
> DESCR('Cluster-receiver channel for QM_eai_client')
> DEFINE CHANNEL(TO.EAI_SERVER) +
> CHLTYPE(CLUSSDR) TRPTYPE(TCP) +
> CONNAME('javector-server.javector.com') CLUSTER(EAI) +
> DESCR('Cluster-sender channel going to QM_eai_server')
> ** Define local queue to receive responses
> DEFINE QLOCAL('EAI_RESPONSES') REPLACE +
> CLUSTER(EAI) +
> DESCR('For receiving responses from services') +
> DEFPSIST(YES) SHARE
>
> 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
>
> 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
>
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
This e-mail and any files transmitted with it, are confidential to National Grid and
are intended solely for the use of the individual or entity to whom they are
addressed. If you have received this e-mail in error, please reply to this message
and let the sender know.
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
Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
Thanks. Out of curiosity, why does Windows have this separate set of amqmdain
commands? What does amqdain stand for??
Thanks,
Mark
> -Original Message-
> From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Chan,
> Ian M
> Sent: Monday, March 29, 2004 8:07 PM
> 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 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
> services. Look at the System Admin Guide Chapter 17 for the
> detail command
> syntax.
>
> Cheeers,
>
> Ian
>
> -Original Message-
> From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf
> Of Mark D.
> Hansen
> Sent: Tuesday, 30 March 2004 10:44 AM
> To: [EMAIL PROTECTED]
> Subject: runmqlsr vs. MQSC "START LISTENER" on Windows ??
>
>
> 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
> dltmqm QM_eai_client
> crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q
> QM_eai_client
> runmqlsr -t tcp -m QM_eai_client -p 1414
> strmqm QM_eai_client
> strmqcsv QM_eai_client
> runmqsc QM_eai_client
> And here is the file "client.mqsc" ...
>
> ** MSQC commands to set up the Client
> ** Make the QMGR a Cluster Repository
> ALTER QMGR REPOS(EAI)
> ** Join the EAI cluster
> DEFINE CHANNEL(TO.EAI_CLIENT) +
> CHLTYPE(CLUSRCVR) TRPTYPE(TCP) +
> CONNAME('eai-client2.javector.com') CLUSTER(EAI) +
> DESCR('Cluster-receiver channel for QM_eai_client')
> DEFINE CHANNEL(TO.EAI_SERVER) +
> CHLTYPE(CLUSSDR) TRPTYPE(TCP) +
> CONNAME('javector-server.javector.com') CLUSTER(EAI) +
> DESCR('Cluster-sender channel going to QM_eai_server')
> ** Define local queue to receive responses
> DEFINE QLOCAL('EAI_RESPONSES') REPLACE +
> CLUSTER(EAI) +
> DESCR('For receiving responses from services') +
> DEFPSIST(YES) SHARE
>
> 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
>
> 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
>
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
Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
It is meant to be a "reboot" of the queue manager to empty everything out and start
again fresh. This is a queue manager that I use in a test/development environment.
> -Original Message-
> From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Tim
> Armstrong
> 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
>
> -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 Windows ??
>
>
> 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
> dltmqm QM_eai_client
> crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q
> QM_eai_client
> runmqlsr -t tcp -m QM_eai_client -p 1414
> strmqm QM_eai_client
> strmqcsv QM_eai_client
> runmqsc QM_eai_client
> And here is the file "client.mqsc" ...
>
> ** MSQC commands to set up the Client
> ** Make the QMGR a Cluster Repository
> ALTER QMGR REPOS(EAI)
> ** Join the EAI cluster
> DEFINE CHANNEL(TO.EAI_CLIENT) +
> CHLTYPE(CLUSRCVR) TRPTYPE(TCP) +
> CONNAME('eai-client2.javector.com') CLUSTER(EAI) +
> DESCR('Cluster-receiver channel for QM_eai_client')
> DEFINE CHANNEL(TO.EAI_SERVER) +
> CHLTYPE(CLUSSDR) TRPTYPE(TCP) +
> CONNAME('javector-server.javector.com') CLUSTER(EAI) +
> DESCR('Cluster-sender channel going to QM_eai_server')
> ** Define local queue to receive responses
> DEFINE QLOCAL('EAI_RESPONSES') REPLACE +
> CLUSTER(EAI) +
> DESCR('For receiving responses from services') +
> DEFPSIST(YES) SHARE
>
> 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
>
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
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 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 services. Look at the System Admin Guide Chapter 17 for the detail command syntax. Cheeers, Ian -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Mark D. Hansen Sent: Tuesday, 30 March 2004 10:44 AM To: [EMAIL PROTECTED] Subject: runmqlsr vs. MQSC "START LISTENER" on Windows ?? 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 dltmqm QM_eai_client crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q QM_eai_client runmqlsr -t tcp -m QM_eai_client -p 1414 strmqm QM_eai_client strmqcsv QM_eai_client runmqsc QM_eai_clienthttp://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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
Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
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 Windows ?? 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 dltmqm QM_eai_client crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q QM_eai_client runmqlsr -t tcp -m QM_eai_client -p 1414 strmqm QM_eai_client strmqcsv QM_eai_client runmqsc QM_eai_clienthttp://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.
Re: runmqlsr vs. MQSC "START LISTENER" on Windows ??
Affiliated Computer Services Stewart Herd Senior Software Engineer [EMAIL PROTECTED] National Software Centre Loughmahon Technology Park Mahon Co. Cork Ireland tel: +353 (021) 2309331 fax: +353 (021) 2307070 mobile: +353 (086) 1713777 -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 "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 dltmqm QM_eai_client crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q QM_eai_client runmqlsr -t tcp -m QM_eai_client -p 1414 strmqm QM_eai_client strmqcsv QM_eai_client runmqsc QM_eai_clienthttp://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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
runmqlsr vs. MQSC "START LISTENER" on Windows ??
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 dltmqm QM_eai_client crtmqm -c "A client queue manager." -u SYSTEM.DEAD.LETTER.QUEUE -q QM_eai_client runmqlsr -t tcp -m QM_eai_client -p 1414 strmqm QM_eai_client strmqcsv QM_eai_client runmqsc QM_eai_clienthttp://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: runmqlsr -i vs BlockIP
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- 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 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 _ Dream of owning a home? Find out how in the First-time Home Buying Guide. http://special.msn.com/home/firsthome.armx 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
Re: runmqlsr
Title: Message Point taken and thanks for mentioning it. Nevertheless, I don't think a PORT() parameter on the START LISTENER command would be a bad idea! Cheers, Paul -Original Message-From: John Scott [mailto:[EMAIL PROTECTED]Sent: 21 February 2004 12:33To: [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 specify the port number on all your channels. 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 this has the limitation that listeners can only use the default port 1414 unless you're on z/OS (I've often wondered why this is ) Cheers, Paul -Original Message-From: Darren Douch [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 a look through the manuals and haven't found anything. Thanks again. Darren.***Click here to visit the Argos home page http://www.argos.co.ukThe information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee.The views expressed may not be official policy, but the personal views of the originator.If you are not the addressee, any disclosure, reproduction, dissemination or use of this communication is not authorised.If you have received this message in error, please advise the sender by using the reply facility in your e-mail software.All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed.
Re: runmqlsr
Title: Message 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 specify the port number on all your channels. 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 this has the limitation that listeners can only use the default port 1414 unless you're on z/OS (I've often wondered why this is ) Cheers, Paul -Original Message-From: Darren Douch [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 a look through the manuals and haven't found anything. Thanks again. Darren. *** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using the reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed.
Re: runmqlsr
Thanks for the responses. Seems like the
answer is that there is no autostart mechanism for the listener, so we need to
do it ourselves. We currently use inetd, but are looking to move over to
the listener to take advantage of the threaded channels in 5.3.
Thanks
Darren.
- 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 1414 unless you're on z/OS (I've often wondered why this is
)
Cheers,
Paul
-Original Message-From: Darren Douch
[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
a look through the manuals and haven't found anything.
Thanks again.
Darren.
Re: runmqlsr -i vs BlockIP
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 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
Re: runmqlsr -i vs BlockIP
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. BTW, do you work round the clock? Your messages appear at anytime! :-) Thanks again for your clarifications. Cheers, Ian -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt, 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 definition. BlockIP is completely different and neither the runmqlsr -i parameter nor the LOCLADDR channel attribute replace it. -- T.Rob -Original Message- From: Chan, Ian M [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 9:47 PM To: [EMAIL PROTECTED] Subject: runmqlsr -i vs BlockIP 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 MQ connection. Any comment? Cheers, Ian 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 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 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 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
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 1414 unless you're on z/OS (I've often wondered why this is ) Cheers, Paul -Original Message-From: Darren Douch [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 a look through the manuals and haven't found anything. Thanks again. Darren.
Re: runmqlsr -i vs BlockIP
Ah! I misunderstood from the descriptionso the BlockIP exit is still required. BTW, do you work round the clock? Your messages appear at anytime! :-) Thanks again for your clarifications. Cheers, Ian -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Wyatt, 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 definition. BlockIP is completely different and neither the runmqlsr -i parameter nor the LOCLADDR channel attribute replace it. -- T.Rob -Original Message- From: Chan, Ian M [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 9:47 PM To: [EMAIL PROTECTED] Subject: runmqlsr -i vs BlockIP 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 MQ connection. Any comment? Cheers, Ian 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 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 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
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 definition. BlockIP is completely different and neither the runmqlsr -i parameter nor the LOCLADDR channel attribute replace it. -- T.Rob -Original Message- From: Chan, Ian M [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 9:47 PM To: [EMAIL PROTECTED] Subject: runmqlsr -i vs BlockIP 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 MQ connection. Any comment? Cheers, Ian 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 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
runmqlsr -i vs BlockIP
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 MQ connection. Any comment? Cheers, Ian 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
Re: runmqlsr
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/software/integration/mqfamily/library/manualsa/amqaac03/amqaac03tfrm.htm Edit the file /etc/services. If you do not have the following line in that file, add it as shown: 2. MQSeries 1414/tcp # MQSeries channel listener Note: You must be logged in as a superuser, or as root, to perform step 1 to step 3. Edit the file /etc/inetd.conf. If you do not have the following line in that file, add it as shown: 4. MQSeries stream tcp nowait mqm /usr/mqm/bin/amqcrsta amqcrsta Note: If you are not creating venus.queue.manager as the default queue manager (in step 4) on this workstation, add -m venus.queue.manager to the end of this line to specify the name of the queue manager to use. Enter the command refresh -s inetd. Polly -Original Message- From: Darren Douch [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 1:46 PM To: [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 a look through the manuals and haven't found anything. Thanks again. Darren.
Re: runmqlsr
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: [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 a look through the manuals and haven't found anything. Thanks again. Darren.
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 a look through the manuals and haven't found anything. Thanks again. Darren.
Re: SWOT Analysis with listeners as inetd or runmqlsr AND channel s as threads or processes
Another way around this with INETD is to disable execution permissions on amqcrsta_nd. We experienced this because SeeBeyond connection factory was hammering the connection when it was lost due to the QMGR coming down. bobbee From: John Scott <[EMAIL 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 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 accept incoming connections and spawn a process to handle it. This caused problems when attempting to restart the qm. It said that processes were still running that use MQ and refused to restart. With runmqlsr, you could end the listener and allow the queue manager to restart and then start the listener, thus controlling remote access to the qm (via client connections and/or channels). Regards John. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: 17 March 2003 13:24 To: [EMAIL PROTECTED] Subject: Re: SWOT Analysis with listeners as inetd or runmqlsr AND channels as threads or processes 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]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: SWOT Analysis with listeners as inetd or runmqlsr AND > channels as threads or processes >Date: Mon, 17 Mar 2003 09:47:36 +1100 > > >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/IP connection on a UNIX systerm server, . If you use inetd, a >process sis started for each connection you define. If you use the >RUNMQLSR command, a thread is started for each connection. This method >can therefore be more efficient. > >I have seen both working well on small systems, however for systems >that have several thousand client connections we use inetd. > >Regards >Tim A > > > > > "Stephan C. Moen" > <[EMAIL PROTECTED]>To: >[EMAIL PROTECTED] > Sent by: MQSeriescc: > List Subject: SWOT Analysis >with listeners as inetd or runmqlsr AND channels as > <[EMAIL PROTECTED] threads or processes > N.AC.AT> > > > 15/03/2003 16:03 > Please respond to > MQSeries List > > > > > >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 thread or process. > > > > > >Ib m not looking for book responses, just REAL-LIFE experiences, >especially from a performance, reliability, scalability, and MQSeries >Version (5.3, 5.2 and below) perspective. Thank you. > > > > > >Steve Moen > > > > > > > > > > > _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail 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 ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication
Re: SWOT Analysis with listeners as inetd or runmqlsr AND channel s as threads or processes
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 accept incoming connections and spawn a process to handle it. This caused problems when attempting to restart the qm. It said that processes were still running that use MQ and refused to restart. With runmqlsr, you could end the listener and allow the queue manager to restart and then start the listener, thus controlling remote access to the qm (via client connections and/or channels). Regards John. -Original Message- From: Robert Broderick [mailto:[EMAIL PROTECTED] Sent: 17 March 2003 13:24 To: [EMAIL PROTECTED] Subject: Re: SWOT Analysis with listeners as inetd or runmqlsr AND channels as threads or processes 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]> >Reply-To: MQSeries List <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: SWOT Analysis with listeners as inetd or runmqlsr AND > channels as threads or processes >Date: Mon, 17 Mar 2003 09:47:36 +1100 > > >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/IP connection on a UNIX systerm server, . If you use inetd, a >process sis started for each connection you define. If you use the >RUNMQLSR command, a thread is started for each connection. This method >can therefore be more efficient. > >I have seen both working well on small systems, however for systems >that have several thousand client connections we use inetd. > >Regards >Tim A > > > > > "Stephan C. Moen" > <[EMAIL PROTECTED]>To: >[EMAIL PROTECTED] > Sent by: MQSeriescc: > List Subject: SWOT Analysis >with listeners as inetd or runmqlsr AND channels as > <[EMAIL PROTECTED] threads or processes > N.AC.AT> > > > 15/03/2003 16:03 > Please respond to > MQSeries List > > > > > >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 thread or process. > > > > > >Ib m not looking for book responses, just REAL-LIFE experiences, >especially from a performance, reliability, scalability, and MQSeries >Version (5.3, 5.2 and below) perspective. Thank you. > > > > > >Steve Moen > > > > > > > > > > > _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail 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 ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ** 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
Re: SWOT Analysis with listeners as inetd or runmqlsr AND channels as threads or processes
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]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: SWOT Analysis with listeners as inetd or runmqlsr AND channels as threads or processes Date: Mon, 17 Mar 2003 09:47:36 +1100 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/IP connection on a UNIX systerm server, . If you use inetd, a process sis started for each connection you define. If you use the RUNMQLSR command, a thread is started for each connection. This method can therefore be more efficient. I have seen both working well on small systems, however for systems that have several thousand client connections we use inetd. Regards Tim A "Stephan C. Moen" <[EMAIL PROTECTED]>To: [EMAIL PROTECTED] Sent by: MQSeriescc: List Subject: SWOT Analysis with listeners as inetd or runmqlsr AND channels as <[EMAIL PROTECTED] threads or processes N.AC.AT> 15/03/2003 16:03 Please respond to MQSeries List 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 thread or process. Ib m not looking for book responses, just REAL-LIFE experiences, especially from a performance, reliability, scalability, and MQSeries Version (5.3, 5.2 and below) perspective. Thank you. Steve Moen _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail 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
Re: SWOT Analysis with listeners as inetd or runmqlsr AND channels as threads or processes
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/IP
connection on a UNIX systerm server, . If you use inetd, a process sis
started for each connection you define. If you use the RUNMQLSR command, a
thread is started for each connection. This method can therefore be more
efficient.
I have seen both working well on small systems, however for systems that
have several thousand client connections we use inetd.
Regards
Tim A
"Stephan C. Moen"
<[EMAIL PROTECTED]>To: [EMAIL PROTECTED]
Sent by: MQSeriescc:
List Subject: SWOT Analysis with listeners
as inetd or runmqlsr AND channels as
<[EMAIL PROTECTED] threads or processes
N.AC.AT>
15/03/2003 16:03
Please respond to
MQSeries List
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 thread or process.
I’m not looking for book responses, just REAL-LIFE experiences, especially
from a performance, reliability, scalability, and MQSeries Version (5.3,
5.2 and below) perspective. Thank you.
Steve Moen
Ëk¹Ëb¢{ ¢¹¨" ¨º¹X§X¬¶˛±Êâ¦بªަº/ם{ax¸¬¶ǫ¼g§z¶¥Rǫ°k¢uæ¯j)ZnW¶m§ÿðÃ
l¡û\¢`+r¯zm§ÿ!Â'§iƭüÄz¸±ª܆+Þ
SWOT Analysis with listeners as inetd or runmqlsr AND channels as threads or processes
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 thread or process. I’m not looking for book responses, just REAL-LIFE experiences, especially from a performance, reliability, scalability, and MQSeries Version (5.3, 5.2 and below) perspective. Thank you. Steve Moen
Re: Old School RUNMQLSR
>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 in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Old School RUNMQLSR
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
Re: Old School RUNMQLSR
Thanks, Paul. Mike Davidson TSYS MQSeries Tech Support [EMAIL PROTECTED] Paul Clarke <[EMAIL PROTECTED]> Sent by: MQSeries List <[EMAIL PROTECTED]> 01/16/2003 11:15 AM Please respond to MQSeries List To: [EMAIL PROTECTED] cc: 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 different now. With previous versions, the listener window would give little status messages as things would happen concerning the >listener program (such as: "Channel program started."). I thought that to be pretty useful at times. With 5.3, there are no longer any of these messages showing up in the listener >command prompt window. No big deal, really. I just was wondering what has happened, or what am I doing wrong. I checked out the syntax in the manual to see if there was some new >parameter(s) that needed to be typed in, but I found nothing mentioning this feature. >Just curious. >Mike Davidson Hi Mike, MQ 5.3 has changed to use what we call channel pools. Essentially when an inbound channel connects to a listener, MQ passes the connection to one of a pool of processes rather than just start a thread inside the listener. Consequently the channel actually now runs inside a background process (AMQRMPPA) which does not have a console window. We made this change for scaleability reasons. In 5.2 it is possible to run out of per process resource (ie. maximum number of threads) when you start many connections into your listener. In 5.3, since this restriction is removed, you can now keep on connecting channels until you run out of some system wide resource which is fixable by buying a bigger machine (:-) though not always). As mentioned before the channel still writes the channel start message, it just goes to the event log (on Windows) and the AMQERR01.LOG file. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley 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
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 different now. With previous versions, the listener window would give little status messages as things would happen concerning the >listener program (such as: "Channel program started."). I thought that to be pretty useful at times. With 5.3, there are no longer any of these messages showing up in the listener >command prompt window. No big deal, really. I just was wondering what has happened, or what am I doing wrong. I checked out the syntax in the manual to see if there was some new >parameter(s) that needed to be typed in, but I found nothing mentioning this feature. >Just curious. >Mike Davidson Hi Mike, MQ 5.3 has changed to use what we call channel pools. Essentially when an inbound channel connects to a listener, MQ passes the connection to one of a pool of processes rather than just start a thread inside the listener. Consequently the channel actually now runs inside a background process (AMQRMPPA) which does not have a console window. We made this change for scaleability reasons. In 5.2 it is possible to run out of per process resource (ie. maximum number of threads) when you start many connections into your listener. In 5.3, since this restriction is removed, you can now keep on connecting channels until you run out of some system wide resource which is fixable by buying a bigger machine (:-) though not always). As mentioned before the channel still writes the channel start message, it just goes to the event log (on Windows) and the AMQERR01.LOG file. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Hursley 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
Re: Old School RUNMQLSR
Yep...I know about those. I just thought it was neat how they would show up in the actual Listener window. Is this 'functionality' no longer there. Not trying to be picky - just curious. Mike Davidson TSYS MQSeries Tech Support [EMAIL PROTECTED] Peter Heggie <[EMAIL PROTECTED]> 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.. 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 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 would give little status messages as things would happen concerning the listener program (such as: "Channel program started."). I thought that to be pretty useful at times. With 5.3, there are no longer any of these messages showing up in the listener command prompt window. No big deal, really. I just was wondering what has happened, or what am I doing wrong. I checked out the syntax in the manual to see if there was some new parameter(s) that needed to be typed in, but I found nothing mentioning this feature. Just curious. Mike Davidson TSYS MQSeries Tech Support [EMAIL PROTECTED] 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
Re: Old School RUNMQLSR
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 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 would give little status messages as things would happen concerning the listener program (such as: "Channel program started."). I thought that to be pretty useful at times. With 5.3, there are no longer any of these messages showing up in the listener command prompt window. No big deal, really. I just was wondering what has happened, or what am I doing wrong. I checked out the syntax in the manual to see if there was some new parameter(s) that needed to be typed in, but I found nothing mentioning this feature. Just curious. Mike Davidson TSYS MQSeries Tech Support [EMAIL PROTECTED] 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
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 different now. With previous versions, the listener window would give little status messages as things would happen concerning the listener program (such as: "Channel program started."). I thought that to be pretty useful at times. With 5.3, there are no longer any of these messages showing up in the listener command prompt window. No big deal, really. I just was wondering what has happened, or what am I doing wrong. I checked out the syntax in the manual to see if there was some new parameter(s) that needed to be typed in, but I found nothing mentioning this feature. Just curious. Mike Davidson TSYS MQSeries Tech Support [EMAIL PROTECTED]
Re: AIX runmqlsr problem
Hello Erik, I think it is inetd. But you can use lsof command to learn about it for sure. try lsof | grep FMCQ. lsof is available on Solaris out-of-box and also there is a freeware implementation on AIX (see http://aixpdslib.seas.ucla.edu/). Pavel Erik Klemetti cc: Sent by: MQSeriesSubject: Re: AIX runmqlsr problem List 09/04/2002 07:16 PM Please respond to MQSeries List Hi Warren, Result from /etc/services fmclFMCQM5010 5010/tcp # MQSeries Workflow Listener for Queue Manager Result from netstat -a tcp4 0 0 *.fmclFMCQ *.* LISTEN This is becoming a bit confusing, it seems like there is something listening BUT I can't 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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
Re: AIX runmqlsr problem
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 List 09/04/2002 06:01 PM Please respond to MQSeries List Hi all, I have a problem with starting a listner and can't figure out why. Probably just a tinny 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 & 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 rigth direction it would be greatly appriciated. /Erik Erik Klemetti Adress: IBM de Venezuela, S.A Edif. IBM, Av. Ernesto Blohm, Chuao, Apartado 64778 Caracas 1060-A Venezuela Tel. +58 416 6073 874 _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com 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 -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. 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
Re: 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/inetd.conf file and see if there are references to MQSeries. This should key you off as to whether the listening facility is "installed" or not. Also, if an entry in /etc/inetd.conf must be added, make sure that you do a "refresh -s inetd" after you edit the file. An example of what the entry in /etc/inetd.conf should look like, refer to the MQSeries Getting Started guide. The entry in /etc/inetd.conf might look something like: MQSeries stream tcp nowait mqm /usr/lpp/mqm/bin/amqcrsta amqcrsta -m Just for your information, the first entry, "MQSeries" will (or should) match an entry in the /etc/services file. Port number usage can be controlled by the matching entry in the /etc/services file. For all you know, it could be that your queue manager listener could already be running and you never knew it. -Warren At 11:16 PM 9/4/2002 +, you wrote: >Hi Warren, > >Result from /etc/services > >fmclFMCQM5010 5010/tcp # MQSeries Workflow Listener for Queue Manager > >Result from netstat -a > >tcp4 0 0 *.fmclFMCQ *.* LISTEN > >This is becoming a bit confusing, it seems like there is something listening >BUT I can't 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 runmqlsr problem >>Date: Wed, 4 Sep 2002 15:24:35 -0700 >> >>There's a possibility that something is using port 5010 already. The >>"netstat -a" command might tell you something. >> >>-Warren >> >>At 10:01 PM 9/4/2002 +, you wrote: >>>Hi all, >>> >>>I have a problem with starting a listner and can't figure out why. >>>Probably just a tinny 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 & >>> >>>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 rigth direction it would be >>>greatly appriciated. >>> >>>/Erik >>> >>> >>> >>> >>> >>> >>> >>>Erik Klemetti >>>Adress: >>>IBM de Venezuela, S.A >>>Edif. IBM, Av. Ernesto Blohm, >>>Chuao, Apartado 64778 >>>Caracas 1060-A >>>Venezuela >>>Tel. +58 416 6073 874 >>> >>> >>>_ >>>Join the world s largest e-mail service with MSN Hotmail. >>>http://www.hotmail.com >>> >>>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 >> >>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 > > > > >Erik Klemetti >Adress: >IBM de Venezuela, S.A >Edif. IBM, Av. Ernesto Blohm, >Chuao, Apartado 64778 >Caracas 1060-A >Venezuela >Tel. +58 416 6073 874 > > >_ >Join the world s largest e-mail service with MSN Hotmail. >http://www.hotmail.com > >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 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
Re: AIX runmqlsr problem
Hi Warren, Result from /etc/services fmclFMCQM5010 5010/tcp # MQSeries Workflow Listener for Queue Manager Result from netstat -a tcp4 0 0 *.fmclFMCQ *.* LISTEN This is becoming a bit confusing, it seems like there is something listening BUT I can't 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 runmqlsr problem >Date: Wed, 4 Sep 2002 15:24:35 -0700 > >There's a possibility that something is using port 5010 already. The >"netstat -a" command might tell you something. > >-Warren > >At 10:01 PM 9/4/2002 +, you wrote: >>Hi all, >> >>I have a problem with starting a listner and can't figure out why. >>Probably just a tinny 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 & >> >>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 rigth direction it would be >>greatly appriciated. >> >>/Erik >> >> >> >> >> >> >> >>Erik Klemetti >>Adress: >>IBM de Venezuela, S.A >>Edif. IBM, Av. Ernesto Blohm, >>Chuao, Apartado 64778 >>Caracas 1060-A >>Venezuela >>Tel. +58 416 6073 874 >> >> >>_ >>Join the world s largest e-mail service with MSN Hotmail. >>http://www.hotmail.com >> >>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 > >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 Erik Klemetti Adress: IBM de Venezuela, S.A Edif. IBM, Av. Ernesto Blohm, Chuao, Apartado 64778 Caracas 1060-A Venezuela Tel. +58 416 6073 874 _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com 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
Re: AIX runmqlsr problem
There's a possibility that something is using port 5010 already. The "netstat -a" command might tell you something. -Warren At 10:01 PM 9/4/2002 +, you wrote: >Hi all, > >I have a problem with starting a listner and can't figure out why. >Probably just a tinny 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 & > >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 rigth direction it would be >greatly appriciated. > >/Erik > > > > > > > >Erik Klemetti >Adress: >IBM de Venezuela, S.A >Edif. IBM, Av. Ernesto Blohm, >Chuao, Apartado 64778 >Caracas 1060-A >Venezuela >Tel. +58 416 6073 874 > > >_ >Join the world s largest e-mail service with MSN Hotmail. >http://www.hotmail.com > >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 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
Re: AIX runmqlsr problem
Erik, it sounds like some other process already has port 5010 in use. I can't tell you exactly from the top of my head, but a netstat -a should give you a listing of all ports that processes are listening on. You can also check if you have an entry in /etc/services for that port number. 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 figure out why. >Probably just a tinny 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 & > >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 rigth direction it would be >greatly appriciated. > >/Erik > > > > > > > >Erik Klemetti >Adress: >IBM de Venezuela, S.A >Edif. IBM, Av. Ernesto Blohm, >Chuao, Apartado 64778 >Caracas 1060-A >Venezuela >Tel. +58 416 6073 874 > > >_ >Join the world s largest e-mail service with MSN Hotmail. >http://www.hotmail.com > >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 _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com 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
AIX runmqlsr problem
Hi all, I have a problem with starting a listner and can't figure out why. Probably just a tinny 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 & 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 rigth direction it would be greatly appriciated. /Erik Erik Klemetti Adress: IBM de Venezuela, S.A Edif. IBM, Av. Ernesto Blohm, Chuao, Apartado 64778 Caracas 1060-A Venezuela Tel. +58 416 6073 874 _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com 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
