Phil, I agree with your point completely, however on other platforms they are very comfortable with spinning up a copy of the DBMS on a backup LPAR to rollback/commit the database entries and then do the backup on a clean database. I'm sure a similar method would work on MVS with DB2.
There is still the problem of 2-phase-commit and associated metadata. Your DB2 database may be nice and clean, but what about your associated CICS/VSAM, IMS, CA-IDMS or Adabas files? I'm not aware that they have a similar Log Suspend function to DB2, and the mind boggles as to how it would be coordinated across each DBMS and file systems to produce federated consistency. That's why I like timestamp and hardware based consistency more than software driven. Anyone working with federated transactions across distributed databases in Client/Server land will know what a let-down software based consistency can be. Ron > > the only issue I see is that if you want a nice consistant database that > is already complete just like it had been > shut down in an orderly manner and didn't need any recovery at all, > then a quiece before flash copy commencement would be needed. > ---------------------------------------------------------------------- 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
