In a recent note unmask]> said: > Date: Mon, 29 Aug 2005 18:05:42 -0500 > > All such schemes tend to run aground on the problem that the reason the > ENQ was there in the first place was to avoid corrupting the dataset(s) > in question. If there was no need for such serialization the ENQ > wouldn't be there in the first place. > No.
There is, for example, no reason to prevent concurrent use of like data set names on different volumes, yet it happens. There is no need; only design expediency. Not all ENQs, nor all their effects, are necessary. --gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
