I haven¹t tried redefining the DCSS yet, but I have tried changing the SAMPLE CONFIG SIZE from 1500 to 2000, and I¹ve tried increasing the virtual machine size from 140meg to 256meg. Neither has any effect on the problem.
-- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 3/30/10 10:26 AM, "Robert J McCarthy" <bob.mccar...@custserv.com> wrote: > Robert, > Before resizing the MONDCCS , you might try the following procedure that I > received from IBM a while back: > 1. Stop PERFKIT > 2. CP MONITOR STOP > 3. CP MONITOR SAMPLE (Note the monitor sample size) > 4. CPMONITOR SAMPLE CONFIG SIZE XXXX (XXXX= size plus 400 to start) > 5. Restart PERFKIT > This worked for me. > Bob > > > > From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf > Of Michael MacIsaac > Sent: Tuesday, March 30, 2010 11:17 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Perfkit SAMPLE CONFIG size too small > > > Robert, > >> > I¹m getting the message ³FCXPMN446E Incomplete monitor data: SAMPLE CONFIG >> size too small² when perfsvm comes up. > > I've seen this a number of times too. We added a section 12.2.4 in the new > z/VM 6.1 /SLES 11 Virtualization Cookbook (top of the page > http://linuxvm.org/present/ <http://linuxvm.org/present/> ) > > It recommends deleting the existing MONDCSS saved segment and redefining a new > one with the commands > ==> defseg mondcss 2200-4fff sc rstd > ==> saveseg mondcss > > Oops, in re-reading this section, I see we omitted words to the effect of "Be > sure there are no other DCSSs saved in the address range of 2200-4FFF". > > I believe there is a similar section, but with more detail, in the VM Basics > Redbook. > > Hope this helps. > > "Mike MacIsaac" <mike...@us.ibm.com> (845) 433-7061