Right there with you - last IPL of the prod system was Feb 26th, all LOCAL page datasets are sitting @ 20%, I was told this was NORMAL for DB2
----- Original Message ----- From: "Tom Conley" <[email protected]> To: [email protected] Sent: Tuesday, April 11, 2017 1:52:06 PM Subject: Re: Paging subsystems in the era of bigass memory On 4/11/2017 2:46 PM, Jesse 1 Robinson wrote: > The problem we face is 'paging creep'. Right after IPL, systems show 0% ASM > usage for some period of time. Then usage starts to creep up until we get > warnings, then eventually hit the no-more-SVC-dumps condition. Adding memory > to an LPAR slows the creep but cannot seem to stop it altogether. The problem > is most pronounced on systems with large DB2 apps. > > Part of the problem, I learned some time back at SHARE, is that there is no > mechanism to 'reclaim' page slots that no longer need to remain on disk. Once > storage gets paged out, it sits there like a sandbag until the owning task is > stopped. Contrast that with JES2 spool track reclaim, which constantly > munches through spool like Pacman and frees up unneeded space. > > . > . > 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] > Preach it Brother Skip!! After IPL, I'm at 0%. A week in, 15%, a month in, 44%. If this is indeed a "feature", then we need to create a requirement to fix this. Tom ---------------------------------------------------------------------- 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
