Re: MQLSX support to be extended and availability to be restored
Marty, Is the extension supported on Windows/XP? MA7D can no longer be downloaded. Jim Marty FrasierTo: [EMAIL PROTECTED] [EMAIL PROTECTED]cc: Sent by: MQSeries List Subject: MQLSX support to be extended and availability to be restored [EMAIL PROTECTED] 11/07/2002 01:26 PM Please respond to MQSeries List This not an official announcement but I thought it would of great interest to the MQLSX users of the world. Support for MQLSX will be extended through 12/31/2004 for Notes/Domino R5 only. MQLSX will not be supported on Notes/Domino R6. In the near future, the MQLSX supportpacs will once again be available at www.ibm.com/software/ts/mqseries/txppacs/ and appears it will be supported for use with MQ 5.2 and WMQ 5.3. For the official verbage and more info there's a technote, #196114, which can be found at this URL -- http://www-1.ibm.com/support/docview.wss?rs=203q=196114uid=sim16e837a58432d7f5985256c68005e47e4 Regards, Marty Frasier [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 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: inet2 vs MQ listener (UNIX) - Answered
Justin, I tried to look at the script on the testcase sight, but it is no longer there. Is there somewhere I can get a copy of it? Thanks, Jim Justin Fries To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: Re: inet2 vs MQ listener (UNIX) - Answered [EMAIL PROTECTED] 07/30/2003 02:37 PM Please respond to MQSeries List Hello, In MQSeries 5.2 and previous releases, runmqlsr ran each inbound connection as a new thread within itself. If runmqlsr ran out of resources--memory, threads, file descriptors--then it would not accept any new connections. This massively threaded approach worked well on systems with a limited number of channels, but on very busy systems it was necessary to set up multiple listeners and balance connections across them. On the other hand, the inetd daemon starts a new amqcrsta process for each inbound connection. There is no chance an amqcrsta responsible for only one channel will run out of resources, so even the busiest of queue managers requires only a single port in inetd. However, this massively unthreaded approach means that busy systems may have hundreds of amqcrstas, forcing administrators to increase maxuproc. Inetd has no idea when the queue manager is inactive, so it will start amqcrstas even when the queue manager is shut down. Some people work around this by disabling the MQ service(s) in inetd; Others simply turn off the execute bits on amqcrsta to avoid the need for root authority. Anybody using inetd might take a look at the script ftp://testcase.boulder.ibm.com/ts/fromibm/mqseries/amqcrsta.ksh (there for a limited time only) which tries to solve this problem in a slightly more elegant way. Despite the limitations of inetd, the fact that it has no limit on the number of simultaneous connections is crucial. This is the single mark against runmqlsr, and on very busy systems it is enough to prevent people from using the listener. WebSphere MQ 5.3 removes the listener scalability problem once and for all. Rather than running each inbound connection as a thread within itself, runmqlsr now passes connections to one of the amqrmppa channel pooling processes. These amqrmppa's are threaded, but not massively so; This means they do not exhaust per-process resources or force administrators to increase maxuproc. The listener will start new amqrmppa's as needed, so a single listener can now handle an unbounded number of connections. The listener is aware of the queue manager's status at all times, so it is also very quick to deny connections when the queue manager is down. The channel initiator in 5.3 also uses the amqrmppa processes, so it is now less likely to exhaust its own resources. Since runmqchi never had to contend with client connections, I think this kind of failure is relatively unheard of compared to runmqlsr running out of resources. Cheers, Justin T. Fries WebSphere MQ Support Raleigh, North Carolina Email: [EMAIL PROTECTED] Robert Broderick [EMAIL PROTECTED] To: Sent by: MQSeries List [EMAIL PROTECTED] [EMAIL PROTECTED] cc: Subject:Re: inet2 vs MQ listener (UNIX) 07/30/2003 02:04 PM Please respond to MQSeries List The basics sound the same as it did in 5.2. What I recall is that around 500 and above connections, for some reason, the runmqlsr's knees started to get wobbely. I am interested in this as there are discussions going on here to move to runmqlsr after upgrading to 5.3. I just wanted to know if there was some factual data behind the recomondation. They were having the QMGR down, bad app keeps connecting and the strmqm comand cannot catch a breath problem. just want to make sure that it was a god move except for the fact that IBM invested some money in desktime to do a little improvement. bobbee From: Tom Schneider [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: inet2 vs MQ listener (UNIX) Date: Wed, 30 Jul 2003 11:53:43 -0400 Bobbee, The MP61 support pack has a pdf WebSphere MQ for AIX - Performance Evaluations which has some explanation.It includes a number of comparisons of inetd and runmqlsr performance, and compares both methods between 5.2 and 5.3 as well. Section 2.2.3 of MP61 contains this text: the 'runmqlsr' has a reduced resource utilisation (one thread per connection vs. a process per connection for the 'inetd' listener and a smaller memory footprint), so is now the preferred method of running client channels and server channels. -Tom == Tom Schneider / IBM Global
Re: Lost messages
I am quessing that you are using sender/receiver channels between the two queue managers. Have you checked that the remote queue definition and the transmit queue have persistent of yes. How do you know that the actual messages being lost have persistent=yes? Jim Joe H. Smith To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: M Subject: Lost messages Sent by: MQSeries List [EMAIL PROTECTED] 09/29/2003 03:25 PM Please respond to MQSeries List We have a situation that I need help finding the cause. Application A running on Queue manager A on iSeries 5.1 sends messages to Application B running on Queue manager B on iSeries 5. MQ5.2 CSD07 on both machines We have found that when Queue manager B is down for IPL we will loose messages from Application A . These are persistent messages. I am looking for a way to track the messages from point a to point b. This will help prove this is either a MQ problem or a application issue. Joan Hughes IT Specialist (Embedded image moved to file: pic21424.gif) Phone: 608-827-3523 Fax: 608-662-6523 I am only as strong as the cocktails I drink, the hairspray I use and the friends I have. * [This message and its contents have been scanned for viruses] * (See attached file: pic21424.gif) attachment: pic21424.gif
Re: SIlent Install - WMQ53 CSD for Windows
Here is some information that I got from IBM on amqicsdn.exe. They told me that they will be added to their documentation. To perform a silent install of a CSD for MQSeries 5.3 1.Download the CSD from the web 2.Run the install program and note the temporary folder the install files are being extracted to. This should be something like 'C:\Program Files\IBM\Source\WebSphere MQ CSD03 EnUs' 3.Exit the CSD install process. 4.'cd' to the temporary directory. 5.'amqicsdn MQPSILENT=1 , would invoke the silent install. . amqicsdn usage flags : MQPLOG : Specifies the log to used during install/uninstall. Eg : MQPLOG=c:\temp\inst.log MQPREBOOT : Specifies if reboot is required. Eg: MQPREBOOT=1 MQPSILENT : Specifies if the installation is silent. Eg: MQPSILENT=1 MQPUNINST : Specifies the uninstallation. Eg: MQPUNINST=1 MQPBACKUPPATH : Specifies the Backup Path. Eg: MQPBACKUPPATH=c:\mqm\backup . Example : amqicsdn MQPLOG=c:\temp\inst.log MQPSILENT=1 MQPBACKUPPATH=c:\mqm\backup . The above assumes you are using the unpacked version of the CSD. If you are using the self-extracting web version, you can either run the downloaded .exe file to unpack first and then do the above, or you can use the following command directly with the downloaded .exe file: . WebSphereMQCSD03EnUs.exe -s -a MQPSILENT=1 . The -s option tells the unpacking to run silently, and the -a option passes the subsequent parameter to amqicsdn.exe. Note the unpacked version will not get deleted in this case. FXA To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: SIlent Install - WMQ53 CSD for Windows [EMAIL PROTECTED] 09/17/2003 12:35 AM Please respond to MQSeries List Has anyone any advice for how to silently install a CSD with WMQ53 for Windows? There is much written about using the response file with setup.exe which was used in 5.2.1, but nothing for the new amqicsdn.exe installer. Any help appreciated. Cheers. 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: Altering queue characteristics
When was it dropped from support and is it being included in the MQ code? Where can I find additional information on this? Thanks. [EMAIL PROTECTED] To: [EMAIL PROTECTED] COM cc: Sent by: MQSeries List Subject: Re: Altering queue characteristics [EMAIL PROTECTED] 09/08/2003 11:35 AM Please respond to MQSeries List I wouldn't use AMI since it is being dropped from support... [EMAIL PROTECTED] ITICORP.COM To: [EMAIL PROTECTED] Sent by: MQSeriescc: List Subject: Re: Altering queue characteristics [EMAIL PROTECTED] n.AC.AT 09/08/2003 11:58 AM Please respond to MQSeries List Hi, You can write a program using the AMI api to alter the queue definitions. Regards, Narasimha Reddy Citigroup Office: +973 588588 - extn 709 Mobile: +973 9034561 Email: [EMAIL PROTECTED] CEEMEA Sales Trading - eCommerce Disclaimer: This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately; you should not copy or use it for any purpose, nor disclose its contents to any other person. -Original Message- From: Larry.Murray [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 6:43 PM To: MQSERIES Cc: Larry.Murray Subject: Altering queue characteristics Good Morning to all, Running MQ 2.1 on OS/390 Is there a program that I can execute in a batch job with control info, that will change a queue from PUT(DISABLED) TO PUT(ENABLED) while MQ is running? Thanks.. Larry Murray Putnam Investments Tech Services 1-617-760-3270 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 communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase Co., its subsidiaries and affiliates. 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
Jim E. Wendorf/Madison/CMG is out of the office.
I will be out of the office starting 06/27/2003 and will not return until 07/14/2003. I will respond to your message when I return. 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
2102 with server bindings
After upgrading an Aix server to v5.3 of Mqseries we are having problems with server bindings connecting to one of our qmanagers. The client connections are working okay. The error that we see when running amqsput is a 2102 - Resource Problem. Any ideas of what we might cause this? 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
