The only I/O Errors that we are seeing are on one of the paging volumes, BDCPG2:

 q alloc page                                        
            EXTENT EXTENT  TOTAL  PAGES   HIGH    %  
VOLID  RDEV  START    END  PAGES IN USE   PAGE USED  
------ ---- ------ ------ ------ ------ ------ ----  
BDCRES 1D60    257    390  24120  18848  24120  78%  
BDCPG1 1D64   1170   2169 180000 125162 180000  69%  
BDCPG2 1D65      1   3338 600840 121703 198393  20%  <== I/O Errors  
                          ------ ------        ----  
SUMMARY                   804960 265713         33%  
USABLE                    804960 265713         33%  
<maint> Ready; T=0.01/0.01 13:58:34                   

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.
Next Steps are:
        4) CP Define cpowned slot 07 BDCPG3   <== Next available slot
        5) DETach 1D67 from MAINT
        6) ATTach 1D67 to system 
        7) CP Start DASD 1D67 page
        8) CP Drain volid bdcpg2 all 
Modify the SYTEM CONFIG file as:
        CP_Owned   Slot   6  BDCPG2             <== Existing         
        Drain      VOLID     BDCPG2 ALL     <== New
        CP_OWNED   SLOT   7  BDCPG3             <== New 


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: Thursday, November 13, 2008 3:52 PM
To: [email protected]
Subject: Re: Risk of Adding a Paging Volume

On Thu, Nov 13, 2008 at 8:36 PM, Wandschneider, Scott <[EMAIL PROTECTED]> wrote:
>  Thanks Dennis.
>
> Maybe with all the response I will get approval or not :)

One more from the peanut gallery... we don't get "I/O problems" on DASD these 
days. That used to be in the old days where we still had platters with rust 
that rotate... ;-) If you really have I/O problems then it would probably 
affect the entire DASD subsystem, so you have also other things to worry about 
(maybe someone on MVS using your volumes for something else?)

It may also be that the page volume was not correctly formatted and CP 
complains and makes you *think* there are I/O problems on the device.
In that case it may be an incorrect operating procedure and your new volume may 
be also bad. The page pack needs to be formatted completely with ICKDSF - not 
just the first cylinder, as some (MVS) storage admin folks are used to. 
Depending on what was there in the past, it may work for part of the volume.
If Q ALLOC shows you only a small number of pages in-use on that volume (about 
the same as the number of errors you had) then that would be my guess.

Rob

Reply via email to