| Author |
Message
|
| bostanian |
 Posted: Wed Nov 18, 2009 8:31 am Post subject: How can I alter LogPrimaryFiles/Secondary vals using cmdline |
 |
|
Newbie
Joined: 28 Jan 2008
Posts: 3
|
Could some one throw some light on how to change the values for
LogPrimaryFiles ,LogSecondaryFiles
For a already running qmanger using command line (for unix)
thanks |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Nov 18, 2009 8:34 am Post subject: Re: How can I alter LogPrimaryFiles/Secondary vals using cmd |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bostanian wrote: |
Could some one throw some light on how to change the values for
LogPrimaryFiles ,LogSecondaryFiles
For a already running qmanger using command line (for unix)
thanks |
Execute the following commands from a command prompt, inserting parameters appropriate for your site:
saveqmgr > backup.txt
endmqm
dltmqm
crtmqm
strmqm
runmqsc < backup.txt
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 18, 2009 8:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
The other, unsupported method, doesn't involve a command prompt (there's no "change log" command") but involves editing the configuration file. A search will turn this up, it's been discussed a few times.
Note that even this doesn't work on a running queue manager. The queue manager will need to be stopped and restarted to change these values.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Nov 18, 2009 9:52 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
There is no need to delete and recreate the QM just to change the # of Log Files. Its 100% supported to end the MQ, change these specific parms and fire the QM back up. The changes may not be evident immediately.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bostanian |
| Posted: Wed Nov 18, 2009 12:30 pm Post subject: |
|
|
Newbie
Joined: 28 Jan 2008
Posts: 3
|
Thanks for your response ( PeterPotkay, Vitor)
Right now on windows I am stopping the qmgr and changing the properties maually - and in linux - I am editing the ini file and bouncing the qmgr..
I am looking for a easy alternate way to automate this process (batch /shellscript)..
Please keep me posted with your suggestions !!
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Nov 18, 2009 1:50 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bostanian wrote: |
I am looking for a easy alternate way to automate this process (batch /shellscript)..
|
There are very few reasons you'd want to do this on a regular enough basis to warrent a script. It's possible (through changing circumstances) for a queue manager to need larger log space than when it was created, but proper planning should ensure enough log space at creation. Certainly if a queue manager runs out of space you should increase the log space further than just to get round the current problem.
There is a school of thought that says a queue manager should be created with logs that fill the available log space on disk.
There are certainly no other methods than the ones described here that will change these parameters.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Nov 18, 2009 3:28 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| There is a school of thought that says a queue manager should be created with logs that fill the available log space on disk. |
There is also a school of thought that says that log file size should be calculated based on current and future usage (growth over time).
Your application developers should provide input on both current and growth.
There is a section of the WMQ System Admin manual that describes how to go about sizing logs.
_________________
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 |
|
|
| Vitor |
| Posted: Thu Nov 19, 2009 6:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| There is also a school of thought that says that log file size should be calculated based on current and future usage (growth over time). |
| bruce2359 wrote: |
| Your application developers should provide input on both current and growth. |
Though there are a number of things application developers should do regarding WMQ that never seem to work out. 
But both of these schools have the log size being set at creation time.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Tue Nov 24, 2009 5:54 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| PeterPotkay wrote: |
| There is no need to delete and recreate the QM just to change the # of Log Files. |
Agree !!!
| bostanian wrote: |
| ...how to change the values for LogPrimaryFiles ,LogSecondaryFiles ... |
You can change this value, but changes do not become effective until the queue manager is restarted, and even then the effect might not be immediate. .. THIS IS THE STATEMENT IN MQ ADMIN. RED BOOK.
It depends at what level you want to make the changes, QMgr or Node level and for that you'll hit the configuration files (in Unix/Aix) i.e. .ini file(s).
Special NOTEs : * The size of the log files specified during queue manager creation cannot be changed for a queue manager. And same is for the Type of Logging you opted while creation of the queue manager.
* LogBufferPages can be increased as Larger buffers lead to higher throughput, especially for larger messages.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 24, 2009 6:15 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| shashivarungupta wrote: |
| ...It depends at what level you want to make the changes, QMgr or Node level and for that you'll hit the configuration files (in Unix/Aix) i.e. .ini file(s). |
OK, I'll bite...Node level?
_________________
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 |
|
|
| shashivarungupta |
| Posted: Tue Nov 24, 2009 6:25 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
| shashivarungupta wrote: |
| ...It depends at what level you want to make the changes, QMgr or Node level and for that you'll hit the configuration files (in Unix/Aix) i.e. .ini file(s). |
OK, I'll bite...Node level? |
Aaaouch !!!
....A WebSphere MQ configuration file (mqs.ini) to effect changes for WebSphere MQ on the node as a whole. There is one mqs.ini file for each node
as :
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
Was that word weird !!!! 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 24, 2009 6:43 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Not quite accurate...
The mqs.ini file provides log defaults for any queue manager created that does NOT have -ll, or -lp -ls etc. specified - it does NOT effect changes on the node as a whole, because that implies it will change an individual queue managers log set-up if the mqs.ini file is changed, and the queue manager is restarted.
_________________
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 Nov 24, 2009 6:44 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| LogFilePages should be higher, I use 16384 |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Tue Nov 24, 2009 6:51 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| exerk wrote: |
Not quite accurate...
The mqs.ini file provides log defaults for any queue manager created that does NOT have -ll, or -lp -ls etc. specified - it does NOT effect changes on the node as a whole, because that implies it will change an individual queue managers log set-up if the mqs.ini file is changed, and the queue manager is restarted. |
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Dec 31, 2009 4:39 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
OK, suppose we have 30 primary log files and we want to reduce this to 20 (of the same size).
We edit qm.ini and change the primary number from 30 to 20.
Stop queue manager
Delete the last 10 log files (QM originally created with 30).
Start queue manager
- or do we have to delete and re-create the queue manager - the manual implies not - but is following the method above safe?
Platform = AIX, WMQ 6.0.2.7
Last edited by zpat on Thu Dec 31, 2009 5:00 am; edited 1 time in total |
|
| Back to top |
|
|
|
|
