I think that the "straw" which finally prompted the elimination of suspend/resume channel programs for paging was a problem exposed by products which DDR swap DASD volumes dynamically.
I suspect the thinking went something like this: Since the problem exposed by DDR swap of page volumes was very severe, the complexity of correctly fixing this problem very high, and the actual performance value of suspend/resume in this day and age now extremely low, why not simply delete suspend/resume complexity from ASM? See OA09675 for more background on this. Brian On Wed, 12 Sep 2007 09:46:24 -0700, Edward Jaffe wrote: >Mark Zelden wrote: >> ... I think the >> decision to remove suspend/resume was based on issues that >> kept cropping up with pav and paging. >> > >Must have been a fairly serious issue of some sort. Why else would they >change the behavior via APAR and not on a release boundary? > >-- >Edward E Jaffe ---------------------------------------------------------------------- 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
