You have to attach the volume to the user performing the DSF.

David Wakser

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Anne D. Crabtree
Sent: Monday, September 24, 2007 8:49 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: ADRDSSU backup of VM volume

cpvol list unit(173f) verify(530W01)                               
 CPVOL LIST UNIT(173F) VERIFY(530W01)                              
ICK32317I 173F DEVICE DOES NOT EXIST                               
ICK31024I UNABLE TO OPEN VOLUME                                    
                                                                   
ICK30003I FUNCTION TERMINATED. CONDITION CODE IS 12                
          08:49:18    09/24/07                                     
                                                                   
ENTER INPUT COMMAND:                                               
end                                                                
 END                                                               
                                                                   
ICK00002I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 12
Ready(00012); T=0.01/0.01 08:49:28                                 
q 173f                                                             
DASD 173F CP SYSTEM 530W01   18   
Ready; T=0.01/0.01 08:49:45       

________________________________

From: The IBM z/VM Operating System on behalf of Kris Buelens
Sent: Mon 9/24/2007 8:43 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: ADRDSSU backup of VM volume


On my 5.3 system, the 530W01 disk has been CP formatted, so I'm
surprised yours seems not to.  So try at least the CPVOL LIST.


2007/9/24, Anne D. Crabtree < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >: 

        First, I assume you mean do this stuff to 530W01...
        Second, the backup ran with the FULL ALLEXCP ADMINISTRATOR.
        Do you think if I RESTORE it the same way, I will be able to use
it?
        I'm really nervous about doing anything to the volume at this
point!  (I know big chicken) 
        
        ________________________________
        
        From: The IBM z/VM Operating System on behalf of Kris Buelens
        Sent: Mon 9/24/2007 3:58 AM
        To: IBMVM@LISTSERV.UARK.EDU
        Subject: Re: ADRDSSU backup of VM volume 
        
        
        I guess that 510W01 was never formatted with CPVOL.  Because,
CPVOL is supposed to not only create CP's allocation bytemap, but also a
VTOC telling z/OS (& co) that the disk is full.
        So,
        
        
        1.      Assure you have no minidisk on 510W01 starting in
cylinder 0 (you can ignore the minidisk of user $ALLOC$)
        2.      Run ICKDSF, press enter twice (to indicate CONSOLE as
in- and output
        
        
                1.      Link to a FULLPACK overlay on 510W01, or use
DEFINE MDISK: 
                          cp define mdisk 1234 0 end 510W01
        
                2.      Verify that there is no CP area on the disk (it
should not, otherwise CPVOL would have created a dummy VTOC, but you
wouldn't like to loose a CP area).  Run 
                          cpvol list unit(1234) verify(510W01)
                        I expect it will tell: ICK33001I 510W01 CYLINDER
ZERO NOT IN CP FORMAT.  If it would -unexpectedly- list CP areas (SPOL,
PAGE, DRCT, TEMP, ...  stop here. 
        
                3.      Format cylinder 0:
                          cpvol format unit(1234) verify(510W01)
range(0,0) ) volid(510W01)
                4.      END
        
        3.      DETACH  1234
        
        
        
        2007/9/23, Anne D. Crabtree < [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> >:
        
                Converted to z/vm 5.3 recently.  We normailly backup our
VM pack on Z/OS via ADRDSSU.  I inadvertently left my 530W01 volume out
of the backup procedure.  I added it into current job that backs up my
old 510W01: 
        
                //WORKVALT  EXEC PGM=ADRDSSU
                //SYSPRINT DD SYSOUT=(,),OUTPUT=(*.OUT1)
                //DASD     DD  DISP=OLD,UNIT=3390,VOL=SER=510W01
                //TAPE     DD  UNIT=MAGS,DISP=(,CATLG),
                // DSN= VALT.SY.TP510W01(+1),
                //
DCB=(DUMMYDCB,RECFM=U,LRECL=0,BLKSIZE=0),LABEL=(1,SL,EXPDT=99000),
                //     VOL=(,RETAIN,,10)
                //SYSIN     DD *
                 DUMP IDD(DASD) ODD(TAPE) OPTIMIZE(4) -
                         TRACKS(0,0,10016,14)  CPVOLUME ADMINISTRATOR
                /*
                //WRKVLT53  EXEC PGM=ADRDSSU
                //SYSPRINT DD SYSOUT=(,),OUTPUT=(*.OUT1)
                //DASD     DD  DISP=OLD,UNIT=3390,VOL=SER=530W01 
                //TAPE     DD  UNIT=MAGS,DISP=(,CATLG),
                // DSN=VALT.SY.TP530W01(+1),
                //
DCB=(DUMMYDCB,RECFM=U,LRECL=0,BLKSIZE=0),LABEL=(2,SL,EXPDT=99000),
                //     VOL=(,RETAIN,,10,REF=*.WORKVALT.TAPE) 
                //SYSIN     DD *
                 DUMP IDD(DASD) ODD(TAPE) OPTIMIZE(4) -
                         TRACKS(0,0,10016,14)  CPVOLUME ADMINISTRATOR
        
                I must have done something differently on 5.1 that I
didn't do on 5.3.  WRKVLT53 gets the following error:
                ADR307E (001)-OPNCL(11), UNABLE TO OPEN VOLUME 530W01,
16
        
                Code 16 says "16   The VM-formatted volume does not have
an OS-compatible VTOC beginning
                     on track zero, record five."
                So, now what do I do?  We have DR exercise in two weeks
and I must have a backup of this volume!  We back up linux volumes
using:
                DUMP IDD(DASD) ODD(TAPE) FULL ALLEXCP ADMINISTRATOR 
        
                Would that work?
        
        
        
        


-- 
Kris Buelens,
IBM Belgium, VM customer support 

Reply via email to