It seems DIAGNOSE that was run previous did not find the error?
On 9/22/06, Bruce Black <[EMAIL PROTECTED]> wrote:
> > ..really interested in this thread,.. We have some sysprogs that > maintain their systems that share a disk volume across separate, > nonsysplexed Lpars. Datasets accessed/updated from different systems,.. > no GRS protection. > So I am curious if this is a situation that could clobber a vtoc. No. Updates to the VTOC are protected by an ENQ/RESERVE under resource SYSVTOC/volser. Since these systems are not part of a GRSplex, the hardware RESERVE is actually issued, and it protects the VTOC from concurrent updates that could corrupt it. The one exposure occurs if they have defined the disk as non-shared (SHARED...NO) in HCD/IOCP. In this case the RESERVE is not done, and the exposure for VTOC corruption exists if both systems create, extend or delete datasets from the volume. Having said that, the exposure exists for DATASET corruption, if the same dataset, especially a PDS, is updated from multiple systems concurrently. It is up to the updatng application whether it issues a RESERVE when updating a PDS to serialize updates. -- Bruce A. Black Senior Software Developer for FDR Innovation Data Processing 973-890-7300 personal: [EMAIL PROTECTED] sales info: [EMAIL PROTECTED] tech support: [EMAIL PROTECTED] web: www.innovationdp.fdr.com ---------------------------------------------------------------------- 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
-- Thanks, Mike ---------------------------------------------------------------------- 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
