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
________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Monday, November 26, 2007 10:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Incomplete monitor data: SAMPLE CONFIG size too small I realize that I've been here before, and I remember that the solution had nothing to do with the monitor command or anything else obvious... But I've slept since then and have come up short of the solution. When I start the Performance Toolkit service machine, it gets this exception: FCXPMN446E Incomplete monitor data: SAMPLE CONFIG size too small What is the proper way to track down a solution to this message? I increased the sample config size from 241 to 700, and still get the same error. Increasing it to 1000 gives two errors: FCXPMN446E Incomplete monitor data: SAMPLE CONFIG size too small FCXPMN446E Incomplete monitor data: DCSS size too small I remember that last time, the solution had nothing to do with the DCSS at all, but I've lost any notes I might have had on it. Plus, this time the problem started with the SAMPLE CONFIG message instead of the DCSS message, so I'd like to get some input before I make any major changes... -- .~. Robert P. Nix Mayo Foundation /V\ RO-OE-5-55 200 First Street SW / ( ) \ 507-284-0844 Rochester, MN 55905 ^^-^^ ----- "In theory, theory and practice are the same, but "Join the story... Ride Ural." in practice, theory and practice are different."
