Understood. I just remember Elpida and company saying that a lot of general problems stemmed from a too-small LPAR size. General observation, not an explanation for the current case.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Friday, January 18, 2019 11:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Abend 106 (was Generic query on Region allocation failure) On 1/18/2019 11:02 AM, Jesse 1 Robinson wrote: > Even Peter Relson did not comment on this, but I gotta say it: 2 GB LPAR is > too small. But, just to be clear, increasing the central storage available to this LPAR will *NOT* solve this issue. The 24-bit private area will continue to be 8M. -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
