No matter. No harm would be done.... CPFMTZA wouldn't execute anyway. ;-) Besides, cyl 0 as PAGE would not cause a failure, it's just not "best practices".
Mike Walter Hewitt Associates ----- Original Message ----- From: "Wandschneider, Scott" [EMAIL PROTECTED] Sent: 11/14/2008 07:31 AM MST To: [email protected] Subject: Re: Risk of Adding a Paging Volume Correct - it should read "3) ALLOCATE 0-0 PERM and 1-END PAGE." Good thing email doesn't execute! Scott R Wandschneider Senior Systems Programmer|| Infocrossing, a Wipro Company || 11707 Miracle Hills Drive, Omaha, NE, 68154-4457|| ': 402.963.8905 || Ë:847.849.7223 || :: [EMAIL PROTECTED] **Think Green - Please print responsibly** -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Friday, November 14, 2008 1:19 AM To: [email protected] Subject: Re: Risk of Adding a Paging Volume On Thu, Nov 13, 2008 at 11:10 PM, Wandschneider, Scott <[EMAIL PROTECTED]> wrote: > The only I/O Errors that we are seeing are on one of the paging volumes, > BDCPG2: > I have already done the following in preparation: > 1) ATTach 1D67 to MAINT > 2) CPFMTZA FORMAT 0-end on a new volume, BDCPG3. > 3) ALLOCATE 0-0 PAGE and 1-END PAGE. I suppose you meant to allocate cylinder 0 as PERM rather PAGE (only problem there is that people may assume it is bad). But it looks good in that you format the entire volume, so makes me wonder about the PG2 volume. Like what are you going to do with that once it is not being used anymore by VM ? What can you do to the volume to make I/O errors go away? What I tried to point out is that real I/O errors are handled by the DASD subsystem. It could be that some major hardware problems do result in the device passing errors to the host, but that would probably impact all logical volumes on that particular rank. I would strongly recommend you take the EREP data to a hardware CE to look at the sense codes. Since you only had two paging volumes, the bad volume was hit a lot as well. I recall from earlier discussion that even when CP failed to write the block, it still marks it as in-use (in the old days to avoid writing again in that same spot). So it may be that once you have shutdown all guests that have pages out on disk, there still remains pages allocated. Rob The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
