Perhaps I should not have used the word 'CLONE'. Let me go into more detail. We are going through a major implementation of Siebel & Tibco on Open Systems. This will talk to the mainframe and replace some of the CICS functionality. On the day we go live we want to Flashcopy our Production DB2 Subsystem. We are not going to change the HLQ or anything, it's just a 'backup' (if you like). We are then going to do our migration and testing against the Production DB2. If it all goes well then it will stay as it is. However, if it all goes wrong then to backout we want to bring down the Production DB2 system, vary the drives offline, vary the flashcopy drives online and then bring up the 'backup' Prod DB2 system. Then we are back to where we were before we started. It seems the quickest and easiest (and possibly safest) way for us to have a 'back-out plan'. My concern is around the MVS catalog and the fact that following the testing, if any datasets went multi-volume or extent then the catalog will reflect this. It would then be incorrect should we bring up the backup DB2 system. I guess we could move the entries for that DB2 system into a seperate catalog and flash that as well..... what do you think?
PS we do NOT want to buy a tool to do it... Thanks Tony ---------------------------------------------------------------------- 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
