| Author |
Message
|
| zpat |
 Posted: Mon Aug 16, 2010 9:42 pm Post subject: |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| Surely the behaviour of mqs.ini vs qm.ini will be the same in v7? |
|
| Back to top |
|
 |
| zonko |
| Posted: Mon Aug 16, 2010 11:15 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
I may or may not work for IBM; who can tell? I could easily assert either.
Anyway, since the stanzas in qm.ini are different from those in mqs.ini, it seems a safe bet that it is not possible to set attributes in mqs.ini and for them to be set for all qmgrs. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 17, 2010 12:50 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
FYI...
I have found the time to add the following stanza to a V6.0.2.6 linux-based queue manager:
| Code: |
SSL:
OCSPAuthentication=OPTIONAL |
And the queue manager started successfully; it would appear that 'unrecognised' stanzas are just ignored.
_________________
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 |
|
|
| zpat |
| Posted: Tue Aug 17, 2010 1:05 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Yes, the documentation is sort of ambigous, a clear statement that only the following <insert list> of stanzas are valid in mqs.ini would help or a warning message that an unrecognised one was found and ignored.
Looks like I am going to have to replicate our TCP keepalive & OCSP setting into all the qm.ini files (a rather labourious task). |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Aug 17, 2010 3:57 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| zpat wrote: |
| Yes, the documentation is sort of ambigous, a clear statement that only the following <insert list> of stanzas are valid in mqs.ini would help or a warning message that an unrecognised one was found and ignored. |
It's safer for the doc to not to make statements like this, so that new (possibly undocumented) stanzas and attributes can be added, modified or removed in FixPacks or releases, and it won't invalidate the existing documentation.
Providing the ability to set qmgr runtime defaults in mqs.ini rather than in each qm.ini is also not a very good idea. A change to such a default in mqs.ini could have a well meaning intention for one qmgr, but it may have unwanted effects on another qmgr (the next time it is restarted) 
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Aug 17, 2010 4:21 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| ...well meaning intention for one qmgr, but it may have unwanted effects on another qmgr (the next time it is restarted) |
Excellent point.
The doc does say that .ini files can be edited manually; but lacks sufficient warnings about the law of unintended consequences when making global changes via mqs.ini.
_________________
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 |
|
|
| gbaddeley |
| Posted: Wed Aug 18, 2010 3:40 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| The doc does say that .ini files can be edited manually; but lacks sufficient warnings about the law of unintended consequences when making global changes via mqs.ini. |
I suspect that administrators doing basic MQ installations and queue manager creations would not even need to look at mqs.ini or qm.ini, or edit them. A common reason to edit these files is to move the location of the recovery logs to a file system other than /var/mqm.
The usual caveats apply, as per the Infocenter page http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa12460_.htm
| Quote: |
| Because the WebSphere MQ configuration file is used to locate the data associated with queue managers, a nonexistent or incorrect configuration file can cause some or all MQSC commands to fail. Also, applications cannot connect to a queue manager that is not defined in the WebSphere MQ configuration file. |
_________________
Glenn |
|
| Back to top |
|
|
|
|
