Well, if you need to be more highly available and can't wait for a dump on a VM system, you need more than 1 VM system ;)
I wonder if IBM could speed up the dump writing time? 24 minutes seems like a long time to write 17GB. It's probably writing 1 4k block at a time :) 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 Lee Stewart Sent: Wednesday, November 04, 2009 11:44 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] VM Dump Quandries Large systems can be a challenge... Problem #1 -- Dump time. Customer took an abend on a 190GB VM LPAR. VM started dumping. (We assume it was to be a "small" dump -- just CP areas and the frame table.) Dumping at the rate of "25% every 6 minutes"... (And we're dumping...) The customer IPLed at 12 minutes into the dump because they needed to get their production systems back up. Have any of the other large LPAR shops dealt with this? (Other than SET DUMP OFF ;-) Telling a customer to leave his system down for half an hour for a dump isn't popular... Problem #2 -- Dump size. CP seems to allocate about 17GB for dump space out of the spool. Then to try and process the dump I'd need something like a mod-27 as a single large CMS minidisk... (Or a giant SAN LUN.) Then what? If I'm going to send the dump to IBM, I doubt FTPing a 20GB file is a choice... Back to good old tape? #2a -- does IBM accept huge SPXTAPE DUMPs? Thoughts and suggestions (other than make the LPARs smaller) welcome... Lee -- Lee Stewart, Senior SE Sirius Computer Solutions Phone: (303) 996-7122 Email: lee.stew...@siriuscom.com Web: www.siriuscom.com
