I think we may have solved the problem. The problem is that Storage Management was restoring to a volume that was OS/390 formatted with an index VTOC instead of restoring to a volume that was CP formatted with CPVOL.
According to the book: 6.8.2 Recovering VM-Format Volumes You can use DFSMSdss to recover VM-format volumes that are accessible to your MVS system. The volumes must have OS-compatible VTOCs starting on track zero, record five. DFSMSdss can only retrieve device information from the OS-compatible VTOC, and cannot interpret any VM-specific information on the volume. Use the CPVOLUME keyword and specify the range of tracks to be restored with the TRACKS keyword. Because DFSMSdss cannot check access authorization for VM data, CPVOLUME is only allowed with the ADMINISTRATOR keyword. -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Feller, Paul Sent: Friday, February 20, 2009 3:39 PM To: [email protected] Subject: Re: DFSMSDSS and VM Volumes Here are the control cards we use to restore VM volumes. We don't do any special format of the target disk before the restore. RESTORE - ADMINISTRATOR - TRACKS(0,0,3338,14) - INDD(TAPE1) - OUTDD(DASD) - COPYV - PURGE RESTORE - ADMINISTRATOR - TRKS(0,0,10016,14) - INDD(TAPE1) - OUTDD(DASD) - COPYV - PURGE Paul Feller AIT Mainframe Technical Support -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of James Stracka (DHL US) Sent: Friday, February 20, 2009 2:02 PM To: [email protected] Subject: DFSMSDSS and VM Volumes In preparation for a Disaster Recovery Test the Storage Group tested DFSMSDSS to dump and restore a VM volume. The dump appears to work but the restore failed. Does anybody know what magical incantation, parameter, option or format of the restore to volume needs to be done in order to get the restore to work? I do not wish to start the OS/VTOC on VM volume discussion all over again, I just want to know what has to be done to get DFSMSDSS to correctly DUMP at VM volume to tape then RESTORE that tape to a volume as a VM pack. The following is what I was given: Ok, here is what we have for the dump for 8003 which is VSCO05: DUMP - ADMINISTRATOR - INDDNAME(DISK) - OUTDDNAME(TAPE) - TRACKS(0,0,3338,14) - CPVOLUME - CANCELERROR - OPTIMIZE(4) ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' ADR109I (R/I)-RI01 (01), 2009.051 08:29:29 INITIAL SCAN OF USER CONTROL STATEMEN ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK ADR006I (001)-STEND(01), 2009.051 08:29:29 EXECUTION BEGINS ADR006I (001)-STEND(02), 2009.051 08:30:56 EXECUTION ENDS ADR013I (001)-CLTSK(01), 2009.051 08:30:56 TASK COMPLETED WITH RETURN CODE 0000 ADR012I (SCH)-DSSU (01), 2009.051 08:30:56 DFSMSDSS PROCESSING COMPLETE. HIGHEST READY Here are the restore parameters and error for 8003: - RESTORE - TRACKS(0,0,3338,14) - CPVOLUME - ADMINISTRATOR - INDDNAME(TAPE) - OUTDDNAME(DISK) - PURGE ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE ' ADR109I (R/I)-RI01 (01), 2009.050 08:58:47 INITIAL SCAN OF USER CONTROL STATEME ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK 0ADR006I (001)-STEND(01), 2009.050 08:58:47 EXECUTION BEGINS 0ADR780I (001)-TDFP (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN TRACKS ( 1 RELEASE 8 MODIFICATION LEVEL 0 0ADR307E (001)-OPNCL(11), UNABLE TO OPEN VOLUME VSCO05, 16 0ADR006I (001)-STEND(02), 2009.050 08:58:49 EXECUTION ENDS 0ADR013I (001)-CLTSK(01), 2009.050 08:58:49 TASK COMPLETED WITH RETURN CODE 0008 0ADR012I (SCH)-DSSU (01), 2009.050 08:58:49 DFSMSDSS PROCESSING COMPLETE. HIGHES TASK 001 ADR307E: Explanation: DFSMSdss is unable to OPEN volume volume_serial_number for the reason indicated by the reason code (reason_code). OBTAIN, RDJFCB, or OPEN passed the return code (return_code). The possible reason codes are: 16 The VM-formatted volume does not have an OS-compatible VTOC beginning on track zero, record five. Thank you, Jim
