Hi Yadong, Actually GRS can also be made to handle cross-sysplex DASD sharing, but requires an installation exit ISGNQXIT, to ensure a HW Reserve is used for the cross-sysplex shared volume.(price = performance for integerity)
You can always READ without any risk of corrupting data, so if you know that data is being update only from say ONLY one sysplex, the risk of corruption should be minimal. Just time when you read the data to ensure you get the 'latest' version. IMO If all you intended to use the shared DASD is intermittently to do file transfers, then I would think the GRS with hardware reserve method would work just fine. If you can enforce updates from only one side (ie. via RACF) and time when you read the data then that should work too. Regards, Yi Ming ---------------------------------------------------------------------- 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
