Craig, I believe, based on some evidence I've seen at some client sites, that th e ESAMON numbers are correct while the PTK ones are not. I believe the caus e of ths is the fact that some of the numbers reported by the underlying CP
MONITOR data stream are not quite what they should be, and the folks at Velocity have made an attempt to correct that problem. Hope this helps. DJ On Wed, 20 Dec 2006 14:40:33 -0800, Craig Sutton <[EMAIL PROTECTED]> wrote: >Hello, > I've been comparing the Velocity ESAMON and IBM Performance Toolkit >products on z/VM 5.2, and have noticed that they disagree on the value o f >the SYTSHS_RSASHARE monitor record. According to the IBM doc, the >SYTSHS_RSASHARE monitor record represents "Cardinal count of resident sh ared >frames". When I extract the MRSYTSHS monitor record from ESAMON, I get: > >SYTSHS_RSACTSHR=6300.0 >SYTSHS_RSASHARE=9400.0 > >When I extract the MRSYTSHS monitor record through PTK, I get: > >SYTSHS_RSACTSHR=6300 >SYTSHS_RSASHARE=2409384 > >which corresponds to the 'Shared storage' value reported in PTK STORAGE. >Does anyone know which one's correct? > >Thanks, Craig >
