Thanks, Berry and Bruce!
The FINIS * * A with the delay looks like the simplest way to get the file
closed so I can read it from another user... I'm essentially filtering for
the LNXAPPL records for the Linux monitoring records. I'm particularly
interested in the mon_fsstatd records, but the oth
You can use 'diskslow' to write the records, but that might not be a
good idea for all of the monitor data unless you are only writing the
records you want and filtering out the rest. The other thing you
should do is set up a delay stage and issue a FINIS every so often (10
secs, 30 secs, whatever
*/
'| 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:linux-...@vm.marist.edu] On Behalf Of
Sc
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 Rohl
Nice idea! We aren't shipping our monwrite data anywhere, so I'll give
this a try for awhile. Thanks again, Berry -
Scott Rohling
On Thu, Oct 21, 2010 at 1:13 PM, Berry van Sleeuwen <
berry.vansleeu...@xs4all.nl> wrote:
> The most easiest:
>
> "PIPE STARMON | > monwrite file a", that way you
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
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 a
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
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
