| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| What is the IPCCSingleSegment in the qm.ini? |
« View previous topic :: View next topic » |
| Author |
Message
|
| sirbrian |
 Posted: Mon May 11, 2009 2:31 am Post subject: What is the IPCCSingleSegment in the qm.ini? |
 |
|
Newbie
Joined: 11 Jun 2007
Posts: 9
|
Hi,
I am looking at an MQ5.3 queuemanager which has an entry
IPCCSingleSegment=268435456:0x80000000
in the qm.ini. I am not sure what this is or how it is entered in the qm.ini. Does anyone know? Is it generated at queuemanager creation.
Thanks |
|
| Back to top |
|
 |
| vol |
| Posted: Tue May 12, 2009 1:21 am Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009
Posts: 69
|
no it is not generated.
try asking the system admin why he put it in there. |
|
| Back to top |
|
|
| sirbrian |
| Posted: Tue May 12, 2009 2:02 am Post subject: |
|
|
Newbie
Joined: 11 Jun 2007
Posts: 9
|
The person who built the qm in the first place has left and didn't document there build process. I think its to do with permitting large messages through the system but I'm not sure.
Anyway I rebuilt the queuemanager (to change logging from linear to circular) and added the entry verbatim to the new qm.ini file and the app is working fine with no MQ errors. Whatever it does its still doing. |
|
| Back to top |
|
|
| gunter |
| Posted: Tue May 12, 2009 5:08 am Post subject: |
|
|
Partisan
Joined: 21 Jan 2004
Posts: 307
Location: Germany, Frankfurt
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 12, 2009 5:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It certainly looks a lot like it's specific to AIX shared memory segments. It may no longer be necessary at all, being replaced more or less by proper use of the EXTSHM env. variable.
If it's not documented in the Sys Admin guide, then it could be a tuning parameter that is documented in the performance reports. You might have to dig around to find an old one for version 5.3, though.
It's a judgement call to say whether you're running a bigger risk leaving it in than you are taking it out. You may want to open a low priority PMR just to get an explanation of what it does and whether it's still applicable at all to your environment.
Are you running other things on the same machine, perhaps WAS, that might need to make use of the shared memory tables? This could have been put in to control what size segments the qmgr reserves, to ensure that it uses a smaller number of segments to leave them for something else. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
