Alan, I'm curious how long had the lpar (system) been up when this issue happened.
I've seen issues with the number of non-reusable ASIDs growing over time related to how long a lpar is up and how active things are related to cross memory connects. What I'm getting at is if you have some tasks that stay up for the life of the IPL that have cross memory connections to other tasks that get cycled from time to time your non-reusable ASID count could grow to a point that you run short. I see this normally with things like Db2 subsystems that normally stay up for the life of the IPL. At least that’s how I understand it. Jim Mulder, please correct me if I'm incorrect in my comments. 😎 Paul -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Alan Haff Sent: Thursday, March 14, 2024 5:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ASVT & ASID discrepancy mystery On Thu, 14 Mar 2024 16:49:03 -0500, Alan Haff <alan.h...@microfocus.com <mailto:alan.h...@microfocus.com> > wrote: >RIDS/IEAVXSRM#L RIDS/#UNKNOWN AB/S0AC7 PRCS/001B0000 REGS/0D218 >REGS/041B8 Ok, I looked up 001B0000 and yeah, it's just indicating we had an IEA059E. So no surprise there. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu <mailto: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
