| Author |
Message
|
| Gideon |
 Posted: Fri Sep 25, 2009 2:02 pm Post subject: WMQ 7 and LogFilePage |
 |
|
Chevalier
Joined: 18 Aug 2009
Posts: 403
|
IN WMQ 7 (either WIndows or AIX)
Can I change LogFilePages, LogPrimaryFiles, or LogSecondaryFiles in qm.ini or the Registry in WMQ 7 or do I have to perform a crtmqm command
Thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Sep 25, 2009 2:07 pm Post subject: Re: WMQ 7 and LogFilePage |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Gideon wrote: |
Can I change LogFilePages, LogPrimaryFiles, or LogSecondaryFiles in qm.ini or the Registry in WMQ 7 or do I have to perform a crtmqm command
|
The only supported way to change these parameters is to delete and redefine the queue manager.
If you change the values & restart the queue manager, the queue manager will be in an unsupported configuration. LogFilePages cannot be changed in this way, the number of primary & secondary files should not be increased this way. AFAIK reducing these values this way causes problems (but why would you reduce them).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gunter |
| Posted: Sun Sep 27, 2009 11:27 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
| Vitor wrote: |
| the number of primary & secondary files should not be increased this way |
Why not? Please explain. Is there anything in the docs or missed I a known problem?
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Sep 27, 2009 12:17 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You can't / shouldn't change log file pages after a QM has been created, but the other log parameters can be changed after the fact.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Sep 27, 2009 4:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| gunter wrote: |
| Vitor wrote: |
| the number of primary & secondary files should not be increased this way |
Why not? Please explain. Is there anything in the docs or missed I a known problem? |
The only supported way to change the primary / secondary files is to delete & redefine the queue manager. Doing what you're suggestion ought to work, usually works on v5.3 & v6 but I doubt has been tried on v7 much yet. It ought to work, but any problems are on you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| gunter |
| Posted: Sun Sep 27, 2009 11:39 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
Vitor, Sorry but I couldn't believe it, so I searched. I found this in the Information Center MQ V7.0:
http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp
| Quote: |
1. You can change the number of primary and secondary log files each time the queue manager starts.
2. You cannot change the log file size; you must determine it before creating the queue manager.
|
_________________
Gunter Jeschawitz
IBM Certified System Administrator - Websphere MQ, 5.3 |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Mon Sep 28, 2009 12:10 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
LogPrimaryFiles/LogSecondaryFiles
| Quote: |
| The value is examined when the queue manager is created or started. You can change it after the queue manager has been created. However, a change in the value is not effective until the queue manager is restarted, and even then the effect might not be immediate. |
I'd say you are all right. You can change them but that the behaviour in picking up the changes might be slightly unpredictable. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 28, 2009 7:12 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Always happy to learn! 
Personally, I remain unconvinced this is a method I'll be using. That "may not be immediate" is slightly alarming to those of us who value certainty (ex-mainframe guy).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Mon Sep 28, 2009 10:58 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Vitor wrote: |
| "may not be immediate" is slightly alarming to those of us who value certainty (ex-mainframe guy). |
Well that aint me....
To me, the "may not be immediate" means the log files may not be created upon restart for example if they are not needed in the case of the secondary log files but I agree the wording may be a little unclear. I still expect this approach to be supported though. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Oct 01, 2009 12:55 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
I've increased the number of log files many times (in accordance with the documentation) and it always works. As others mentioned, you cannot change the size of the files and the number of pages.
I can't believe I am braver than Vitor. Something is awry in the universe. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Oct 01, 2009 1:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| SAFraser wrote: |
| I can't believe I am braver than Vitor. Something is awry in the universe. |
The fact that I have a brain the size of a planet does not give me nerves of steel. It just gives me more room for the paranoia.
You must also remember that years in the industry has left me nearly bald (partially through stress, partially through ripping it out). Hence it is never good.
I thank you for posting your experience; there's nothing better than real-world experience from the proverbial coal face.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 01, 2009 1:10 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Vitor wrote: |
| ...You must also remember that years in the industry has left me nearly bald (partially through stress, partially through ripping it out). Hence it is never good... |
Which is why the dungeon drains keep blocking... 
_________________
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 |
|
|
| Cressida |
| Posted: Thu Aug 25, 2011 2:34 am Post subject: |
|
|
Disciple
Joined: 13 Jul 2007
Posts: 157
|
With upfront apology to the community for opening a few older posts re managing MQ Logs (changing attributes, circular vs linear, inability to do media recovery on circular logs, ...) ........., we at Cressida wanted to bring a new announcement to people's attention some:
For a long time we have been hearing and reading how the Distributed platforms WMQ administrators and systems staff have been looking for and wanting more built in WMQ Log Management functionality as found in the zOS WMQ environment. Well, we have done something about that !
Introduction of a new Log Manager component in ReQuest for WMQ Version 5.0:
• Log Manager introduces extensive functionality for manipulating and changing all WebSphere MQ queue manager attributes stored in .ini files and/or the Windows Registry. The list of features include the ability to switch between linear/circular logging and changing the size and attributes of the log files. If the changes made require that the queue manager is physically recreated, Log Manager ensures that all existing objects and messages are preserved during the process.
• Log Manager brings WMQ administrators the added built-in functionality to create archive copies (optionally compressed) of the active log files, regardless of whether the Queue Manager uses linear or circular logging. When using linear logging, log files that have been archived and are no longer needed for (WMQ) recovery, are automatically deleted from the active directory. When using circular logging, ReQuest’s Recover function can be used to recover from media failures.
I hope this helps to re-generate a few healthy discussions on the subject.
Thank you. |
|
| Back to top |
|
|
|
|
