| Author |
Message
|
| Nitgeek |
 Posted: Tue Sep 10, 2013 3:19 am Post subject: Unable to find mqs.ini in windows |
 |
|
Novice
Joined: 21 Feb 2012
Posts: 21
|
I am unable to locate mqs.ini file. I have WMQ 7.0 installed in my Windows 7 machine.
The workpath parameter in "HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion" is "C:\Program Files\IBM\WebSphere MQ"
But there is no mqs.ini file here. Infact, I did a search in my whole c drive but I was unable to locate this file.
I want to set an existing queue manager as default queue manager without MQ explorer. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Sep 10, 2013 3:47 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The information you are looking for is stored in the Registry on Windows platforms. You can use the amqmdain administrative application to set the default qmgr.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Tibor |
| Posted: Tue Sep 10, 2013 4:30 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| Remembering the good old days when .ini files were in use on Windows platform as well... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 10, 2013 4:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I've never had a strong need for a default queue manager, and always found it somewhat troublesome when there was one.
It's been worth the small extra effort to perform the necessary configuration to ensure that each application knows what queue manager to talk to. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Sep 10, 2013 4:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I believe that on Windows mqs.ini, qm.ini, and qmstatus.ini were not 'available' until WMQ V7.1. Prior to that, as bruce2359 has already pointed out.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 10, 2013 4:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| I've never had a strong need for a default queue manager, and always found it somewhat troublesome when there was one. |
 somewhat
It can be helpful to have a configuration where if an application doesn't know what queue manager to use, it doesn't just latch onto the default one & blow up with a 2085.
It's also valid to have the application latch onto the one default queue manager that exists in whatever environment it happens to be running in and use that.
Horses for courses and all that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Sep 10, 2013 5:55 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
I've seen people accidentally make changes in PROD due to a default Qmgr being set and they didn't specify the QmgrName. If you force them to provide the QmgrName and they are on the PROD box but give a DEV QmgrName, it will safely fail.  |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 10, 2013 6:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| JosephGramig wrote: |
| I've seen people accidentally make changes in PROD due to a default Qmgr being set and they didn't specify the QmgrName. If you force them to provide the QmgrName and they are on the PROD box but give a DEV QmgrName, it will safely fail. |
Another valid use case.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Sep 10, 2013 3:19 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| JosephGramig wrote: |
| I've seen people accidentally make changes in PROD due to a default Qmgr being set and they didn't specify the QmgrName. If you force them to provide the QmgrName and they are on the PROD box but give a DEV QmgrName, it will safely fail. |
That's the exact reason why I always recommended that the "default" queue manager feature of MQ should NEVER BE USED. 
I rejoiced that mqs.ini, qm.ini and qmstatus.ini files reappeared in Windows MQ v7.1 & 7.5.
_________________
Glenn |
|
| Back to top |
|
|
|
|
