Paul, I will play with this tonight and get back to you offline by tomorrow.
-----Original Message----- From: Paul Clarke [mailto:[EMAIL PROTECTED] Sent: Monday, September 15, 2003 1:25 PM To: [EMAIL PROTECTED] Subject: Re: Strange behavior with a Temp. Dynamic queue Peter, I've just tried it again on my system and all works as expected. I think perhaps we should take this offline. The key question, from my point of view, is whether MO71 is at fault here or the product or is this some form of limitation. Firstly, if you issue the same set of commands from RUNMQSC do you see different behaviour ? Secondly, when you issue a STOP CHANNEL a lot depends on what type of stop you issue as to what happens. For example, if you issue a QUIESCE stop then you are reliant on the application using the FAIL_IF_QUIESCING option on the MQI calls to notice that the channel has been quiesced. (Clearly you are also reliant on the application taking any notice of the return codes). Try my MA01 support pac as a test since this uses FAIL_IF_QUIESCING as all good MQ apps should. Thirdly, if you issue a STOP CHANNEL MODE(FORCE) do you get the required behaviour. ie the application ends. Cheers, P. Paul G Clarke WebSphere MQ Development "Potkay, Peter M (PLC, IT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED] cc: RTFORD.COM> Subject: Re: Strange behavior with a Temp. Dynamic queue Sent by: MQSeries List <[EMAIL PROTECTED] AC.AT> 12/09/2003 17:32 Please respond to MQSeries List Paul, I don't think it is working. The queue manager is 5.3 CSD04. I start up a client app (WatchQ) on my desktop, connecting to queue manager ABC. It uses the SVRCONN channel ABC.SVRCONN channel. I then use MO71 to display Channel Status for ABC. Since other apps are also using this channel, I see about 10 entries, including one for my IP address, for this SVRCONN channel. Anytime I click refresh, I see the bytes sent field updated for my instance, as well as al others So now I want to stop this particular instance. I select the entry that has my IP address and double click it. I change the required status to Inactive, select my IP address for the conection name, and select ABC as the QM name, then I click Stop. The message I get is "Stop of channel 'ABC.SVRCONN' accepted." But my client app is not effected. And if I click refresh on the master channel status list, the bytes sent field keeps growing for that instance (and all instances). It does not look like it had any effect. If I try it again, the message comes "'ABC.SVRCONN':Channel not active." But that channel is just fine, as all instances seem to be running A-OK. (The apps are up and the bytes sent fileds grow) If I click start, I get "'ABC.SVRCONN':Channel in use." -----Original Message----- From: Paul Clarke [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 11:48 AM To: [EMAIL PROTECTED] Subject: Re: Strange behavior with a Temp. Dynamic queue >MO71 >If you select Channel Status from the QM menu, you are provided with a list >of all the instances. I right clicked on one of the 10 instances I had for >my SVRCONN channel, and saw it had a STOP option (MQExplorer does not). >So I selected STOP. Oops! The SVRCONN channel went into a Status of >"Multiple". I had to stop and start the SVRCONN channel to get it back. >Is this a supported function of MO71? Peter, I don't think I understand what you're asking, what does status of 'mulitple' mean ? If you're trying to stop a single instance of a running channel then you can do so provided that you're talking to a 5.3 Queue Manager. You can only stop the channel and put it into status inactive though. Bring up the stop channel dialog. Change the required status to Inactive. You should now see two more fields in the dialog which are the connection name and Queue Manager name of the channel instance you wish to stop. Clicking the stop button will now stop all channels matching these values. Note, therefore that if you have 10 clients from the same IP address there is no way to kill just one of them. There is nothing guaranteed to be unique about a channel status entry. The bottom line is that MO71 'should' support the 5.3 MQSC command set. If you find there's something you can do with RUNMQSC that you can't do with MO71 let me know, 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 This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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
