Mark Post wrote: I think you just got yourself into trouble here. I would hardly characterize z/OS as having a "primitive" I/O stack or architecture. Lots of buffering and caching go on there, both in hardware and software. The _real_ difference is that z/OS, just like Linux or z/VM, _always_ has a consistent view of its own data. In a shared DASD environment, this is enforced via serialization techniques, either hardware reserve/release, or software such as GRS, MIM, etc. Without those, backing up one z/OS system from another one would run into similar (but perhaps not as severe) problems with inconsistent data winding up on tape.
Yea I guess so, but not by intention. The wording was not meant to imply "simple" or "bad". I just intended to state, that due to caching the consistent view of the data that Linux has is not permanently reflected on disk. And that is causes trouble when backing up from outside that guest. Carsten ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
