IBM Support

Tuning the ISM QSize parameter correctly in ITCAM for Transactions

Question & Answer


How do you tune the QSize parameter?


The QSize parameter sets the maximum size of a monitor's event queue on disk. Warning messages like the following in the monitor log indicate that you need to increase the QSize:

Queue X full, event from Y is lost!

The guidelines state that the best setting for QSize is 10 MB for most situations (10 * 1024 * 1024 = 10485760 bytes). In larger environments, increase this value for each monitor by 1 MB ( 1024 * 1024 = 1048576 bytes) per 1000 elements.

For the monitors, the default QSize is set to 1024000 bytes. This value is deliberately set to a lower initial value -- just under 1 MB.

The default bridge QSize is higher than the monitor QSize, since all monitor events have to go through the bridge. By default the bridge QSize is initially set to 51200000 bytes. This value is a little less than 50MB (1024 * 1024 * 50 = 52428800 bytes).

If the QSize for the other monitors is being increased then increase the bridge QSize. The amount of increase depends on the total number of elements being processed by all monitors. Set a bridge QSize of between 30MB and 100MB.

To change the QSize parameter, edit the .props file for the bridge, kisagent, or monitor. Then, restart the ISM agent.

The .props files reside in the following directory:

Windows: ITM_HOME\TMAITM6\ism\etc\props
Unix/Linux: ITM_HOME/<ARCH>/is/etc/props

[{"Product":{"code":"SS5MD2","label":"Tivoli Composite Application Manager for Transactions"},"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Component":"ITCAM TRANSACT ISM 5724S79IS v710","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.4","Edition":""}]

Historical Number


Product Alias/Synonym

ISM 7.4;ITCAMfTransactions;T7.4

Document Information

Modified date:
17 June 2018