We use putfiles to write the records, the filename/filetype contains the date and recordID. This is part of a larger pipeline that contains some logic to enable us to comunicatie with the MONWRITE machine.
'\ STARMON MONDCSS SHARED', /* connect to MONITOR */ '| specs 9.8 1.8', /* Get TOD clock */ ' 5 c2x 10 7.2 c2x nw 1-* nw', /* Translate D R */ '| a: lookup 10-16 1-7 details', /* Only selected records */ '| dateconv 1.8 todabs rexxj timeout', /* Convert tot to julian */ '| specs w1 1 /_/ next /00/ next', /* Build filename : 10271_00 */ ' /D/ nw w3 next', /* Build filetype : D0A */ ' /R/ next w4 next', /* Build filetype : R0002 */ ' /D/ nw', /* Build filemode : D */ ' w5-* next', /* Remaining data */ '| putfiles append grouped', /* write files */ '\ < moncolct param x', /* Parameter file */ '| a:' The param file contains the records we want to write to disk such as "0A 0002". If you want files for every hour replace the /00/ with 7.2 . Regards, Berry. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Scott Rohling Sent: vrijdag 22 oktober 2010 1:45 To: [email protected] Subject: Re: mon_fsstatd - filesystem monitor records One thing - I don't seem to actually see the output file on disk until I stop the PIPE.. is there a way to run pipe starmon and have it output records to disk as they are received? When I LINK to the disk from another userid - I don't see a file at all until I 'hx' out of the pipe. Scott Rohling On Thu, Oct 21, 2010 at 1:13 PM, Berry van Sleeuwen < [email protected]> wrote: > The most easiest: > > "PIPE STARMON | > monwrite file a", that way you will write one record > to disk for each record in CP MONITOR. In this case you won't have to > figure out how to parse the records or to process them afterwards with > MONVIEW. Just connect a test CMS machine to MONITOR if you can't use > MONWRITE for this. > > Regards, Berry. > > Op 21-10-10 21:04, Scott Rohling schreef: > > 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 < > > [email protected]> 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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 [email protected] 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/
ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2
