DanGiles
ADSM.ORG Senior Member
TSM 6.2 on linux (on z/VM).
Background: If you give linux lots of memory, it's going to 'use' all of it, mainly in cache. When TSM/DB2 starts up, DB2 will take all the memorylinux will give it.
Question: So, how does one monitor memory usage to find out how well its doing, and determine -- BEFORE an abend -- if you are going to need more memory? (and conversely, if you could remove some memory.) A 'free -m' really doesn't tell you much. TSM support points me to db2pd, but the output is large and means absolutely nothing to me
Waiting for a DB2 'cannot allocate memory' error is really not the way to do capacity planning!
Background: If you give linux lots of memory, it's going to 'use' all of it, mainly in cache. When TSM/DB2 starts up, DB2 will take all the memorylinux will give it.
Question: So, how does one monitor memory usage to find out how well its doing, and determine -- BEFORE an abend -- if you are going to need more memory? (and conversely, if you could remove some memory.) A 'free -m' really doesn't tell you much. TSM support points me to db2pd, but the output is large and means absolutely nothing to me
Waiting for a DB2 'cannot allocate memory' error is really not the way to do capacity planning!
