I can't remember the SMF record details, but the dispatch priority of address spaces can be lowered 'on the fly' via SDSF (or CA's Sysview, if memory serves) to swap them out and prevent them from grabbing storage at the expense of what would now be higher priority ASIDs. HTH.
On 17/03/2022 11:43, Peter wrote: > Hello, > > Could someone please direct me on which SMF record can produce the report > showing the highest CPU consumers who caused the memory shortage ? > > Today in one of our LPARs address space was recursively abending and it > monopolized the memory due to which TCPIP couldnt Dispatch the unit of work > and the Connectivity went down for a while. > > After canceling the abending Address space the LPAR started functioning > back and it was evident that the memory got relieved once the address space > was cancelled. > > Is there any SMF records which can tell me the memory consumption of the > address space which made the other Address space not to dispatch the UOW ? > This report basically will help me to show to my management people who dont > understand mainframe. > > Regards, > Peter > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > . > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
