In a message dated 9/13/2005 6:58:21 P.M. Central Standard Time, [EMAIL PROTECTED] writes:
necessary. You need to allocate a new data set on the target volume covering the tracks you just "backed up" on the source. Then you must run a backup job whose input is the target volume's data set. A read to a target track that has not been changed gets redirected to its corresponding source track, and a read to a changed track goes to the target volume, because the controller copied the source track before allowing the write to take place to that source track. This backup job may take hours, depending on the amount of data to be copied, the interference from other I/O activity, and other things that affect mileage. But the backup copy is all internally consistent as of the fateful moment when those couple of milliseconds went flying by. >> I only used FDRINSTANT. Didn't have to do any of this. Needs a blank target in same storage groups and whoosh it's done. Backups run at same speed as tape controller no slower no faster. ---------------------------------------------------------------------- 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
