Tom wrote on 03/11/2005 02:36:06 AM: > > They missed a very large portion of the puzzle, Chris: Aux. > > IF the DB2 and z/OS designers had ALSO implemented "private paging" for the > (ab)users of virtual storage (like DB2 and perhaps GRS) then they would > have moved all of the controls over to the appropriate groups and all would > (eventually) be right with the world.
Interesting thought. I would only countenance such a process *IF* ASM still controlled everything. I was at one point responsible for large systems that were running M204 - this does (used to ??? - been a while) it's own rendition of page/swapping of users. A total disaster from a (system) performance perspective. > If, for example, a new special DDNAME (like //JOBPAGE or //SYSPAGE) were > also introduced for local paging for such units of work then the rest of > the system's page datasets wouldn't grow so the impact to the non-DB2 > sysprog would have been minimal. The DB2 jockeys could grow their buffer > pools and would only impact themselves if they blew past their > JOBPAGE/SYSPAGE defined limits. They could even potentially allocate their > local paging data sets from their own luxurious DASD plantations... we non- > DB2 types wouldn't care. Might need to implement a paging hierachy to allow ASM to continue to do what it needs to do if subsystem paging was inappropriately allocated. Linux users will be aware of the priority that can be assigned to swap partitions/files - something similar might be useful. Shane ... ---------------------------------------------------------------------- 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
