Re: WMQI V2.1 Control Center Question
I wrote a little script, but this is only working with cygwin (or another posix shell). If any expert can re-write it as a CMD script, just do it... #!/usr/bin/bash # # start mqsi CC with specific Panes.ini file # lcc.sh # if [ `ps -efW | grep -i "mqsi.Tool.bin.java" | wc -l` -eq 0 ]; then LASTCONN=`grep "RepoQueue" Panes.ini | cut -d'=' -f2` cp Panes.ini Panes.$LASTCONN.ini if [[ /$1 != / && -f Panes.$1.ini ]]; then cp Panes.$1.ini Panes.ini fi $SYSTEMROOT/system32/cmd /c mqsilcc.bat $2 $3 else echo "CC is already running! (ENTER)" read fi I placed this file (lcc.sh) into directory \Tool. Tibor > Sort of yes, but, it's pretty brutal. > I had the same issue, and raised the question with Hursley. This information is >stored in a file \tool\panes.ini. One option was that a person could write a script >to edit this file and remove > some of the lines before starting the control center, forcing the connection dialog. > But it was pretty messy figuring out what to remove. Instead, the other option that >they suggested was to just > delete the file. This does force the connection dialog, but it also removes the >graphical information associated with the control center as well as your repository >information. Which gave me more > problems then it solved. > I requested that they make the displaying of the connection dialog at startup either >an option or a feature of the product, but, am not holding my breath on that. > Tim Halbur > -Original Message- > From: Hornby, Derek [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 17, 2003 1:29 PM > To: [EMAIL PROTECTED] > Subject: WMQI V2.1 Control Center Question > ... is there a way of forcing Control Center to always request connection info when >connecting to a remote config manager (instead of just connecting to the last config >manager it was used with) ? > ... that way, I could avoid the scenario where someone opens up Control Center, sees >the Topology in the Config Manager, thinks they are in Dev. , then deletes a few >"unwanted" brokers then --- > oops, > finds that they were connected to a Prod Config Manager ! > forcing the entry of the Connection info every time would at least cause the >user to stop and think ! > 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: WMQI V2.1 Control Center Question
Sort of yes, but, it's pretty brutal. I had the same issue, and raised the question with Hursley. This information is stored in a file \tool\panes.ini. One option was that a person could write a script to edit this file and remove some of the lines before starting the control center, forcing the connection dialog. But it was pretty messy figuring out what to remove. Instead, the other option that they suggested was to just delete the file. This does force the connection dialog, but it also removes the graphical information associated with the control center as well as your repository information. Which gave me more problems then it solved. I requested that they make the displaying of the connection dialog at startup either an option or a feature of the product, but, am not holding my breath on that. Tim Halbur -Original Message- From: Hornby, Derek [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:29 PM To: [EMAIL PROTECTED] Subject: WMQI V2.1 Control Center Question ... is there a way of forcing Control Center to always request connection info when connecting to a remote config manager (instead of just connecting to the last config manager it was used with) ? ... that way, I could avoid the scenario where someone opens up Control Center, sees the Topology in the Config Manager, thinks they are in Dev. , then deletes a few "unwanted" brokers then --- oops, finds that they were connected to a Prod Config Manager ! forcing the entry of the Connection info every time would at least cause the user to stop and think ! 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: WMQI V2.1 Control Center Question
If you have seperate configuration managers for dev, qa and prod this will not be a problem as long as the users id is not in the qa or prod mqbr* groups. >>> [EMAIL PROTECTED] 01/17/03 01:29PM >>> ... is there a way of forcing Control Center to always request connection info when connecting to a remote config manager (instead of just connecting to the last config manager it was used with) ? ... that way, I could avoid the scenario where someone opens up Control Center, sees the Topology in the Config Manager, thinks they are in Dev. , then deletes a few "unwanted" brokers then --- oops, finds that they were connected to a Prod Config Manager ! forcing the entry of the Connection info every time would at least cause the user to stop and think ! 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
WMQI V2.1 Control Center Question
... is there a way of forcing Control Center to always request connection info when connecting to a remote config manager (instead of just connecting to the last config manager it was used with) ? ... that way, I could avoid the scenario where someone opens up Control Center, sees the Topology in the Config Manager, thinks they are in Dev. , then deletes a few "unwanted" brokers then --- oops, finds that they were connected to a Prod Config Manager ! forcing the entry of the Connection info every time would at least cause the user to stop and think ! 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
