Ok... I purged and redefined the DCSS, and now I don¹t get the message; I¹m waiting to see if it really starts collecting.
I did ³DEFSEG 9000-AFFF SC RSTD², matching our previous segment. My questions now are, What happened to the prior segment that caused it to fail? Could the problem have been avoided, and how? Also, now I¹m getting the following two messages, repeatedly, and we¹re still not collecting any data: FCXPMN444E IUCV reply failed with reason code 9 HCPMOV6274I The sample data messages and corresponding records have been purged. So I¹m still looking for a problem source... -- 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:16 AM, "Michael MacIsaac" <[email protected]> wrote: > > 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" <[email protected]> (845) 433-7061
