We are a monoplex z/OS system and will be moving to a new data center late this year. When we move, we will get a new CPU (z9 now) and replace our Shark (2105-800) with something else. Ideally, the desire is to keep our existing system running while testing the new system and do a quick cutover using non-disruptive move software to move DASD volumes from old unit to new.
Now we're thinking, how are we going to move that data? They think we would be down too long to dump and restore (3592). Likewise on physically moving the Shark plus it could be risky. So I ask you big, bad, concurrent copying, GDPSers out there... What are our options for quickly moving about 400 3390-3 and a few 3390-9, or replicating our current volumes to a new unit located a few miles away? I would appreciate any advice or pointers to things I should check out. We will probably have some help from our Business Partner but we need to start thinking things out now. Thanks, Robert Johnston UAMS - Little Rock, AR ---------------------------------------------------------------------- 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
