On Fri, 12 Sep 2008 15:24:15 EDT, IBM Mainframe Discussion List <[EMAIL PROTECTED]> wrote:
>Next came HyperPAV. IOS decides on an I/O by I/O basis if a PAV is needed >for the next I/O, finds one from a pool of available PAV UCBs, directs the new >I/O to a PAVed UCB which the controller knows how to send to the proper >device, then IOS returns the PAV UCB to the pool of available PAV UCBs when the >I/O ends. You don't have to reconfig. You don't wait until the end of the >WLM interval. IOS does no control I/O to tell the controller a new PAV >configuration. Instantaneously dynamic as opposed to quasi-static as opposed to >seriously static. One of the nice things about HyperPAV is that if you share DASD between sysplexes, you don't have to worry about "PAV thrashing" like you would if you had WLM controlled PAVs active to both sysplexes for the same DASD. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
