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]
