On Thu, 19 Feb 2009 07:32:54 -0500, Peter Relson <[email protected]> wrote:
>The health checker address space is not the only address space in z/OS that >has increased its MEMLIMIT so that system code will not be adversely >impacted by whatever value the customer has set. > >Peter Relson >z/OS Core Technology Design > Hi Peter, That wasn't my question / comment. I thought MEMLIMIT=NOLIMIT was identified as X'00000FFFFFFFF000'. That is documented in the MVS Installation Exits for IEFUSI. And this is always what I've seen in the RAX for RAXLVMEMLIM. In z/OS 1.10, that seems to still hold true except for the Health Checker address space. What was seen there by the person who reported this to me was that RAXLVMEMLIM was X'0000100000001002' - a value bigger than 16 exabytes. 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
