Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-12-04 Thread Harding, Mike
I am off on Fridays with even Julian dates and Mondays with odd ones. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of barton Sent: Tuesday, December 04, 2007 1:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Incomplete monitor data: SAMPLE CONF

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-12-04 Thread barton
em [mailto:[EMAIL PROTECTED] On Behalf Of Alan Ackerman Sent: Tuesday, November 27, 2007 9:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Incomplete monitor data: SAMPLE CONFIG size too small See Calculating the Space Needed for the Saved Segment in "z/VM V5R3.0 Performance". Alan Ackerman

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-12-04 Thread Harding, Mike
; (personal) Note: For 2007, I am off on Fridays with even Julian dates and Mondays with odd ones. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Ackerman Sent: Tuesday, November 27, 2007 9:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re:

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-11-28 Thread Rob van der Heij
On Nov 28, 2007 6:02 AM, Alan Ackerman <[EMAIL PROTECTED]> wrote: > interval. There may be a paging cost if you make the EVENT area too big, > since CP keeps adding event data to the end until it is full before wrapping. That penalty is not real because CP will release the frames once all who eat

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-11-27 Thread Alan Ackerman
On Mon, 26 Nov 2007 14:19:07 -0600, RPN01 <[EMAIL PROTECTED]> wrote: >This matches what I got to by trial and error. I¹ve ended up with the >mondcss segment from 9000-9fff, and a sample config size of 1500. It see ms >to be working without error now. This started with installing Omegamon X E >for

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-11-26 Thread RPN01
This matches what I got to by trial and error. I¹ve ended up with the mondcss segment from 9000-9fff, and a sample config size of 1500. It seems to be working without error now. This started with installing Omegamon XE for z/VM and Linux, and I still need to see if that is receiving any data at thi

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-11-26 Thread Rob van der Heij
On Nov 26, 2007 6:54 PM, Feller, Paul <[EMAIL PROTECTED]> wrote: > What I've had to do in the past is increase the DCSS size and the SAMPLE > CONFIG size. We run with a SAMPLE CONFIG size of 1250. The MONDCSS is set > to BEGPAG of 09000 and a ENDPAG of 09FFF. We had to go to 1250 size when we

Re: Incomplete monitor data: SAMPLE CONFIG size too small

2007-11-26 Thread Feller, Paul
What I've had to do in the past is increase the DCSS size and the SAMPLE CONFIG size. We run with a SAMPLE CONFIG size of 1250. The MONDCSS is set to BEGPAG of 09000 and a ENDPAG of 09FFF. We had to go to 1250 size when we added a large amount of new DASD to the VM lpars. Paul