Hi Berry - Thanks very much for your reply - you're right - I was being too simplistic in plumbing the MONWRITE data. I used MONVIEW and quickly did an XLATE A2E against the output - I can now see dasda1, etc in the output. So I obviously need to parse the MONWRITE data correctly. I'll poke around the MONVIEW stuff to figure it out.
Thanks again! Scott Rohling On Thu, Oct 21, 2010 at 12:28 PM, Berry van Sleeuwen < berry.vansleeu...@xs4all.nl> wrote: > Hi scott, > > We do see records for every mounted filesystem. Both on SLES10 SP2 and > SLES11 SP1. Indeed, have option APPLMON for the guest and start > mon_fsstatd. Actually we have APPLDATA, mon_fsstatd and mon_procd running. > > We run two machines on the CP MONITOR running custom plumbing. The first > only writes selected recordtypes to disk (such as Dom. 10 Rec. 2). The > second CMS machine monitors the filesystem records and creates incidents > based on certain thresholds on filesystem usage. > > We don't run the IBM MONWRITE. First of all we'd like to write only > those records we are interested in. And second, MONWRITE writes the file > into fixed 4096 records instead of one record for each monitor record. > > Do you know for sure your plumbing does indeed get the records the > correct way? Have you tried the MONVIEW package from the IBM VM packages? > > Regards, Berry. > > > Op 21-10-10 17:16, Scott Rohling schreef: > > I am trying to use the mon_fsstatd driver (s390-tools) to generate > monitor > > records with Linux fileystem stats. The guest has OPTION APPLMON and > > ability to write monitor records. > > > > Records 'do' seem to be generated - but it seems like it's only for a > single > > filesystem (/dev/dasdd1, which happens to be the last listed if you do a > df > > -h). According to the device drivers manual -- a record should be > > generated for each physical mounted filesystem. I'm only seeing one. > > > > As an aside - I am viewing the records on z/VM by linking to MONWRITE 191 > > and using some creative PIPEing to translate the ascii fields to ebcdic, > > etc... Basically getting all records with 'LNXAPPL' in ascii and > parsing > > them. So pretty sure I'm not missing records that are being written for > > APPLDATA ... > > > > Has anyone else used this driver and gotten different/better results? > > > > (I'm running this on RHEL54 under z/VM 5.4) > > > > Scott Rohling > > > > ---------------------------------------------------------------------- > > For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > > For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
