For you, I hope that never happens, I have some AUX pages that never free, and creep 1% or so every 2 days, been following the discussion and trying to undersand why suddenly DB2 seems to be the culprit, when I've seen DB2 workloads not have an adverse effect on AUX storage, my last IPL of this system was Feb 26th, and we have a Large Frame area defined 7740M
my locals are on Mod9's LOCAL 20% OK 4371 PAGE.SYSA.VSYSPG1.LOCAL LOCAL 20% OK 4471 PAGE.SYSA.VSYSPG2.LOCAL LOCAL 20% OK 4571 PAGE.SYSA.VSYSPG3.LOCAL LOCAL 19% OK 4671 PAGE.SYSA.VSYSPG4.LOCAL LOCAL 19% OK 4771 PAGE.SYSA.VSYSPG5.LOCAL LOCAL 19% OK 4072 PAGE.SYSA.VSYSPG6.LOCAL LOCAL 20% OK 4172 PAGE.SYSA.VSYSPG7.LOCAL LOCAL 20% OK 4272 PAGE.SYSA.VSYSPG8.LOCAL LOCAL 20% OK 4070 PAGE.SYSA.VSYSPGH.LOCAL LOCAL 20% OK 4170 PAGE.SYSA.VSYSPGI.LOCAL LOCAL 20% OK 4270 PAGE.SYSA.VSYSPGJ.LOCAL LOCAL 20% OK 4370 PAGE.SYSA.VSYSPGK.LOCAL LOCAL 20% OK 4470 PAGE.SYSA.VSYSPGL.LOCAL LOCAL 20% OK 4570 PAGE.SYSA.VSYSPGM.LOCAL we have 8 DB2MSTR regions 43 misc regions total (DISTR,IMS...) if I decide not to IPL until June or July I see myself running the risk of getting AUX storage shortages what to do? add some more locals? NO! Carmen ----- Original Message ----- From: "Jesse 1 Robinson" <[email protected]> To: [email protected] Sent: Wednesday, April 12, 2017 12:56:19 PM Subject: Re: Paging subsystems in the era of bigass memory I'd like to pull this discussion back up to the jet stream level. We face the prospect of having to IPL z/OS just to relieve an ASM shortage. Weenie-ware servers seem to run forever without this encumbrance. We put our highest-value mission-critical applications on a platform that cannot keep its own shorts tidy. Enough already. Even if IBM gave us memory for free, we would still have endure interruptions to get it installed. And how much is sufficient? How many interruptions? Throwing more hardware at a software deficiency is not a solution. I'm afraid that some MBA PFK will propose running the whole shebang on *nix. Then where will we (all) end up? . . 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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Marchant Sent: Wednesday, April 12, 2017 10:15 AM To: [email protected] Subject: (External):Re: Paging subsystems in the era of bigass memory On Wed, 12 Apr 2017 12:44:32 -0400, Tony Harminc wrote: >On 12 April 2017 at 10:16, Tom Marchant < >[email protected]> wrote: >[DB2] > >> It still makes no sense to me. It certainly can't read the record >> into the same page, because that would require that the page be paged in >> first. > >I've no idea what it *does* do, but it *could* Page Release the old >page before reading from DASD into it. Thanks, Tony. And BTW, Kees, I should have said "I don't understand" rather than "It makes no sense to me." Subtle difference, perhaps. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
