You don't want to treat the volumes like OS/390 or z/OS volumes by using the FULL parameter. You need to use the TRACKS parameter and specify to dump all the tracks.
Lonny -----Original Message----- From: Scott Chapman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 14, 2003 7:53 AM To: [EMAIL PROTECTED] Subject: Backing up z/VM Linux volumes I'm trying to do a full-volume dump from OS/390 of a z/VM volume that has minidisk on it used for Linux and I'm getting errors indicating a problem with the VTOC. I presume we have an issue with the way we formatted/allocated/something the volume in VM, but so far I haven't been able to figure it out. I've seen the "IBM Linux-z/OS dss dump/restore how-to", but that seems to imply that volumes are assigned completely to Linux and are not VM mini-disks. However, other things seem to imply that I should be able to backup VM volumes from OS/390. (In fact I'm pretty sure we used to do it back when we had VM for non-Linux purposes.) If somebody could point me in the right direction, I would appreciate it! Thanks! Scott Chapman American Electric Power Details follow: PAGE 0001 5695-DF175 DFSMSDSS V2R10.0 DATA SET SERVICES 2003.014 07:21 DUMP FULL INDDNAME(INDD1) - OUTDDNAME( - OUTDD1 - ) - CANCELERROR - ALLEXCP - OPTIMIZE(4) - WAIT(2,2) ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' ADR109I (R/I)-RI01 (01), 2003.014 07:21:53 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED. ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK ADR006I (001)-STEND(01), 2003.014 07:21:53 EXECUTION BEGINS ADR307E (001)-OPNCL(03), UNABLE TO OPEN VOLUME 430U14, 06 ADR006I (001)-STEND(02), 2003.014 07:21:57 EXECUTION ENDS ADR013I (001)-CLTSK(01), 2003.014 07:21:57 TASK COMPLETED WITH RETURN CODE 0008 ADR012I (SCH)-DSSU (01), 2003.014 07:21:57 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM: TASK 001 Which indicates: ADR307E (ttt)-mmmmm(yy), UNABLE TO OPEN VOLUME volume_serial_number, reason_code return_code 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: 4 OBTAIN failure on VTOC's VTOC entry. 6 The VTOC's VTOC entry is not the first record in the VTOC. 8 RDJFCB failure. 12 OPEN failure. 16 The VM-formatted volume does not have an OS-compatible VTOC beginning on track zero, record five. Alternately, I tried: PAGE 0001 5695-DF175 DFSMSDSS V2R10.0 DATA SET SERVICES 2003.013 12:34 DUMP TRACKS(0,0,3339) - INDY(7B14) - OUTDDNAME( - OUTDD1 - ) - CANCELERROR - ADMINISTRATOR - CPVOLUME - OPTIMIZE(4) - WAIT(2,2) ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'DUMP ' ADR109I (R/I)-RI01 (01), 2003.013 12:34:57 INITIAL SCAN OF USER CONTROL STATEMENTS COMPLETED. ADR405E (001)-DYNA (02), DYNAMIC ALLOCATION OF VOLUME 7B14 FAILED. ERROR CODE 0218. INFORMATION CODE 0000. ADR017E (001)-CLTSK(01), 2003.013 12:34:58 TASK NOT SCHEDULED DUE TO ERROR. TASK RETURN CODE 0008 ADR012I (SCH)-DSSU (01), 2003.013 12:34:58 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM: TASK 001 Which seems to also indicate a problem with the VTOC.
