Willie, See the SETSYS CDSVERSIONBACKUP parameter/subparameters.
HSM dumps to the "oldest" (if there are more than 1) versions of the backup dataset. It then renames to the "current version" and remembers the current version. AFAI recall, none of these files are in use except during BACKVOL CDS processing. You should be able to delete/reallocate them on the fly. Reallocate them with the Primary space equal to the current allocation and an appropriate secondary and you should be OK. If the HSM journal fills up all HSM automatic functions (BACKUP, DUMP, etc.) will be placed in "HOLD" status. i.e. HSM will 'go to sleep' until a manual release is performed. The DF/DSS backup will make a backup copy of your MCDS, but will not alleviate the requirement for HSM to Successfully complete a "BACKVOL CDS" command. <snip> ... clearing that up for me. Just to inquire about the suggestion to force a backup - F DFHSM,BACKVOL CDS. I assume that this goes to disk. Am I right? Can I force the backup to tape? If so how would I do that? Also, since I am unable to get this fixed, I have scheduled a shutdown of DFHSM, execute a DFDSS backup of the MCDS to tape. Could you please tell me what is the significance of the disk backup copies? I checked to see if DFHSM is using them (TSO command ISRDDN E) but I don't see anything. What is the danger if I the disk backup has failed? I am not familiar with this portion of DFHSM any information that you could provide would be very helpful. </snip/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
