Here some code from y TSLAMON EXEC that performs some calculations
(CPU usage and WAIT%), These waits is something RTM/ESA nor VMPRF
didn't provide in real-time, hence my -old- code.

    '|Irefr: FaninAny',
    '|R: REXX ('myname mytype')' refresh, /* Perform calculations     */
    '|FILESLOW' fid,
    '?IMMCMD SUSPEND|SPEC /SUSPEND/ 1|Irefr:',
    '?IMMCMD $$REXX$$|INSERT /$$REXX$$ / 1|Irefr:',
   '? starmon mondcss sample',            /* Obtain data              */
    '|R4: STRFIND X4040404004400004',     /* Keep Domain 4, record 4  */
    '|R:',                                /* Pass for calculations    */
    '?R4:|STRFIND X4040404004400003',     /* Also Domain 4, record 3  */
    '|R:',                                /* Pass for calculations    */

The complete TSLAMON EXEC is available on request.

2008/3/18, Schuh, Richard <[EMAIL PROTECTED]>:
> Almost. I would consider the PIPE that uses the starmon stage to be a
>  utility; the stage by itself is simply a tool used to build the utility.
>
>  Regards,
>
> Richard Schuh
>
>
>
>
>  > -----Original Message-----
>  > From: The IBM z/VM Operating System
>
> > [mailto:[EMAIL PROTECTED] On Behalf Of A. Harry Williams
>  > Sent: Tuesday, March 18, 2008 8:59 AM
>  > To: [email protected]
>  > Subject: Re: MONWRITE files
>  >
>  >
>
> > Actually, there already is such a utility program, and it is
>  > shipped with every z/VM system.  It's kept on the 190 or
>  > S-disk so you may not think to look there.  It's called CMS
>  > Pipelines.  There is a STARMON stage for reading data from
>  > the MONDCSS and *MONITOR IUCV service.  There is a DEBLOCK
>  > MONITOR stage for reformating the headers, and there are
>  > LOCATE and other stages for selecting the records desired.
>  > (DFSORT or SYNCSORT is often used for selecting SMF records
>  > on MVS, when lots of SMF records are recorded, but not need
>  > for every process.  Pipelines would be the corresponding tool)
>  >
>  > For more details, PIPE AHELP STARMON, and PIPE AHELP DEBLOCK.
>  >  Also see
>  >
>  >
>  > http://www2.marist.edu/~pipeline/pipeline.news117
>  >
>  > http://www2.marist.edu/~pipeline/pipeline.news1110
>  >
>  >
>  > http://www2.marist.edu/~pipeline/bhelp/ACH0201.html
>  >
>  >
>  >
>  > /ahw
>  >
>  >
>  >
>  > >/Tom Kern
>  > >On Tue, 18 Mar 2008 09:10:12 -0400, Hamilton, Brian
>  > ><[EMAIL PROTECTED]>
>  > >wrote:
>  > >>Hi Stefan,
>  > >>
>  > >>In response to your statement,
>  > >>
>  > >>* the old file is read by a rexx procedure and only a subset of the
>  > >>monitoring records are selected from it building a new file
>  > (about 10%
>  > >>of the original size), this reduced file is then send to
>  > z/OS by ftp
>  > >>for reporting.
>  > >>
>  > >>I'd be interested in what this rexx is extracting.  Our
>  > intent is to
>  > >>produce reports on CPU and memory usage and I agree the
>  > data is huge.
>  > >>
>  > >>Thanks
>  > >>Brian
>  >
>



-- 
Kris Buelens,
IBM Belgium, VM customer support

Reply via email to