Don't worry about maint and tcpip. They run CMS and CMS isn't going to mess with stuff he doesn't need, unlike Linux. CMS understands not to waste your whole VM size with file buffers and cache.
Your guest is bigger than your real storage. If you need to do that overcommitting (and you may not - see Rich's question about SGA sizes), your VM paging system must be robust. Spread it out on as many 3390-3's as it takes to make it no more than 50% full (we prefer -35-40% as there is a knee on the curve right around 50 and things go to hxxx real fast after that ). Don't have anything else on your paging packs. You need to have some Xstore too as David said. On 16G of real, probably 2G. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of August Carideo Sent: Wednesday, June 24, 2009 1:03 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Testing Linux Z/vm We are preparing for a test and loading the database is taking forever. Paging is high. I/O devices are less than 5% busy. CPU is never more than 20%. An Oracle file import is taking over 14 hours. Any Idea's with this little bit of info to go on Also is there a reason for the TCPIP machine to be set at 128M? the real machine is 2 IFLs and 16G of storage. We see the paging coming from the oracle machine( 2CPUs VM size =24G), Maint and TCPIP. Maint was set at 128M and IPLing a non shared copy of CMS. We set Maint to 16M and IPL a shared copy of CMS. His paging has stopped. I would like to set TCPIP at something less that 128M either 16M or 32M to stop his paging. Does this sound right ? Augie