At the point when I see this (just now) here is the IND info: ind AVGPROC-007% 01 MDC READS-000001/SEC WRITES-000000/SEC HIT RATIO-100% STORAGE-067% PAGING-0005/SEC STEAL-000% Q0-00001(00000) DORMANT-00007 Q1-00000(00000) E1-00000(00000) Q2-00000(00000) EXPAN-001 E2-00000(00000) Q3-00006(00000) EXPAN-002 E3-00001(00000)
PROC 0000-007% LIMITED-00000 Doesn't look bad to me - other than the Q3 which may be if I understood it. -------------------------------------------------------------------- Lionel B. Dyck, Systems Software Lead Kaiser Permanente Information Technology 25 N. Via Monte Ave Walnut Creek, Ca 94598 Phone: (925) 926-5332 (tie line 8/473-5332) E-Mail: [EMAIL PROTECTED] Sametime: (use Lotus Notes address) AIM: lbdyck Linux on 390 Port <[EMAIL PROTECTED]> wrote on 04/30/2002 12:13:58 PM: > >I'm seeing a situation under z/vm 4.2 where my sles 7.2 linux guest will > > I would vote for the eligable list. If you have filled up > storage on VM enough and not tuned things properly VM will > be very shy in starting to work on a guest that appears so > demanding as a big Linux machine. Your real time monitor or > performance reporting should be able to tell you whether > people have been in the E3 queue. For starters have a look > at #CP IND to see what your storage utilisation is. > You probably need to set SRM parameters to make it work. > > Rob
