I have trace spooling setup for the IBM.StorageRM daemon and recently the number of trace files being spooled has dramatically increased. The change in usage around TSAMP has been the running of 'lssam' every 10 minutes.
Answer by Gareth Holl (3412) | Mar 27, 2015 at 03:15 PM
'lssam' queries each of the resource managers for each of the managed resources, including the IBM.StorageRM resource manager. Therefore, running 'lssam' frequently will definitely increases the amount of trace data, thus the number of spooled trace files. The extra queries will show up in the StorageRM trace files as extra monitoring messages.
Besides the obvious of limiting the running of 'lssam', there are to areas that can be changed to reduce tracing :
1) Change the _RMF info level to 1 (it is currently set to 2) by running the following as root, on each server :
ctsettrace -s IBM.StorageRM -a "_RMF:Info=1"
refresh -s IBM.StorageRM
2) Increase the monitoring interval level for the storage resources. Default is every 5 seconds:
-----> lsrsrc -c IBM.Disk <-----
Resource Class Persistent Attributes for IBM.Disk
resource 1:
HarvestInterval = 1800
AutoDelete = 0
AutoCorrelate = 1 Page 40 of 41
MonitorInterval = 5
You can play with different levels ... we'd suggest using increments of 5.
To change it, run the following as root on any node:
export CT_MANAGEMENT_SCOPE=2
chrsrc -c IBM.Disk MonitorInterval=30