One of the issues I've noticed is that if the VTOC moves as a function of the FlashCopy, then you may have issues accessing the target volumes, particulrly on other systems. These can usually be solved by varying off/on the target volumes, so that the VTOC location can be refreshed in the UCB.
This is usually an issue only after the first copy of a volume - as long as the source-target pairing remains the same, the VTOC will not appear to move after the first time. I suspect that your problem may be ralated to this. >>> Paul Jodlowski <[EMAIL PROTECTED]> 12/24/2007 11:54:37 AM >>> We have a DS6800 with flashcopy 2. We use the following to flash 37 volumes COPY FULL INDY(USERxx) OUTDY(FSERxx) PUR ADMIN - DUMPCOND FCNC FR(REQ) ALLDATA(*) ALLEXCP The job takes about 20 seconds and completes with a cond code of 0. Then about 4 hours later run job to dump target to tape using following DUMP INDD(DASD) OUTDD(BACKUP) FCWD The job fininhes with cond code 0. The next day when run Copy job again get cond code of 8 with System abend code=0213 (but not on EVERY volume just on 9 of them). If I init the target volumes this seems to fix it. Just want to know if this is S.O.P. (copy,dump then init). Or is this WRONG. os is 1.7 Cheers ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
