So, Chris, are you looking for something like this?

(Real report generated by ESAMAP, but real time could work too)
(this currently checks for the 51 most common errors
that installations make with running linux under z/VM)


MDC8 MDC should be limited to 1GB or lStorage.
      It is currently consuming 2.19 Gigabytes. There
      is no benefit for MDC to be in Expanded rather
      than Real storage.
MDC9 MDC should be disabled for Expanded Storage.
      It is currently consuming 384330 pages. There is
      no benefit for MDC to be in Expanded rather
      than Real storage.
LNS1 Linux server LINUX1 is idle, but is inqueue 100%
     This hinders vm's ability to manage storage.
     Ensure timer patch active and VM is current.
LNS1 Linux server LINUX13 is idle, but is inqueue 100%
     This hinders vm's ability to manage storage.
     Ensure timer patch active and VM is current.
SHR4 Share setting for LINUX14 of 100.000 is too low.
     Each virtual processor has share of 50, this
     results in less performance for server.
SHR4 Share setting for LINUX15 of 100.000 is too low.
     Each virtual processor has share of 50, this
     results in less performance for server.
SHR4 Share setting for LINUX16 of 100.000 is too low.
     Each virtual processor has share of 50, this
     results in less performance for server.
CHN1 Channel 1D busy is 96.5 and is excessive for ESCON.
     Consider more channels, faster channels
     or moving data to other channels.
USQ5 Excessive users (21.5) in Queue 0.
     Using QUICKDSP indiscriminately nulls the
     scheduler to control thrashing.
     If running Linux, SET SRM STORBUF instead.

>Date:         Fri, 3 Dec 2004 09:15:12 -0600
>From: "Little, Chris" <[EMAIL PROTECTED]>
>Subject: Re: Linux Slowdown
>
>But at the same time, understanding what the monitor is telling me is
>absolutely complex.  It's a lot of data to make sense of, especially how it
>coorelates together.  I can get a sense of it, but I'm not sure that if
>something was really wrong I would be able to pinpoint the issue.
>
>-----Original Message-----
>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
>Barton Robinson
>Sent: Thursday, December 02, 2004 4:27 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Linux Slowdown
>
>
>I really DO hate to bring this up, but....
>It really does solve a lot of mysteries to have a performance
>monitor that collects your linux and VM data.
>
>Right now, i'm looking at some SAP data, Linux on z/VM,
>a big linux server logs off and the master processor utilization
>sky rockets, then the i/o from all of the other servers
>stops for a minute. now i know why service was degraded,
>and have enough information to understand the problem.
>Without data, how could i have a clue of which one of
>100 common problems caused my problem this time?







"If you can't measure it, I'm Just NOT interested!"(tm)

/************************************************************/
Barton Robinson - CBW     Internet: [EMAIL PROTECTED]
Velocity Software, Inc    Mailing Address:
 196-D Castro Street       P.O. Box 390640
 Mountain View, CA 94041   Mountain View, CA 94039-0640

VM Performance Hotline:   650-964-8867
Fax: 650-964-9012         Web Page:  WWW.VELOCITY-SOFTWARE.COM
/************************************************************/

----------------------------------------------------------------------
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

Reply via email to