Is the OP talking about running out of space in, e.g., ECSA, or is he talking about running out of page frames. As usual, the devil is in the details and he didn't give any.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Peter Relson [rel...@us.ibm.com] Sent: Sunday, March 20, 2022 8:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: SMF record - Looping and Memory shortage <snip> Cancel with DUMP option will be useful for the product owners but from zOS is there a way to know in which memory block they are consuming more ? </snip> Without reading minds, no. "Memory block" as you are using it has no meaning to the operating system. It only has meaning to the exploiter. Why would you care which memory block an exploiter is using more of? That's something the exploiter (i.e, product owner) would be interested in. Don't you want to know which exploiter is using more of a resource than you want? PFA can help there. Further, what does the fact that this exploiter is using more and more memory have to do with the problem that was encountered? TCP/IP was mentioned. It seems unlikely that TCP/IP has any knowledge of this or would base its actions on this. Obviously anyone running in that address space could encounter problems if they were unable to obtain storage in order to do what they needed to do. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
