Yep, no problem doing that. Just make sure that who ever you are going thru to buy this stuff, knows what you are looking to do.
Flashcopy is an extra charge item. Do you need to buy flash copy for both boxes? If you have PAV (extra charge item on your inhouse box), do you need PAV for your remote box? Will you be charged for microcode (PAV, Flashcopy, etc) on a disaster box as you are not normally charged for software on a disaster box? You can have continous mirroring. But in some cases, you may want to do just weekly flashcopys or incremental flashcopys. You may want to free up communications between the two sites during the day. It's all mix and match, if you pay for it. The OS only gets envolved, if you want it to, to issue the command to the dasd subsystem, to setup and start the flashcopy process, whatever that process is. So, for example, at end of shift, you may have scheduled a flashcopy of certain files that you can restore to (like after a batch job abend). Perhaps takes a cpu second from the mainframe (if something really complicated), then the dasd subsystem takes over. i.e. no use in getting people envolved in something that your scheduler can handle. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 10/26/05 9:27 AM >>> Thanks to all who have replied. Let me explain what I had envisioned. I a mentioned DS8100, but it could be a DS8000. I'm looking for the capability for a local DASD subsystem to mirrored off site to the same type of DASD subsystem and that it be done concurrently. The idea is that this "mirroring" is going on 24/7 and should the main site get hit with a disaster, the off site DASD subsystem would be current up to the point in time of the disaster. I would prefer the two DASD subsystems manage this "mirroring"( or what ever you want to call it) by themselves. That is, no operating system, z/VM, VSE or z/OS has to do it. It seems to me the o/s has better things to do then doing this "mirroring" function, but if it must, it must. Is there such a solution? Thanks again, Steve
