LSQA storage is internally represented by data structures that are very
different from the non-LSQA private area data structures. The LSQA data structures are not task related. For example, subpools 253, 254, and 255 are internally the same subpool, and a single 4K page (and thus a single VSMLIST allocated storage descriptor) can contain storage for all 3 of these subpools. The VSMLIST allocated storage descriptor always says subpool 255, even though it may represent storage obtained via a combination of subpool 253, 254, and 255 requests. For purposes of freeing task or jobstep task owned LSQA, each TCB points to chains of AEs (IHAAE). AEs are not processed by VSMLIST.- Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> wrote on 07/30/2017 12:52:49 PM: > From: Binyamin Dissen <bdis...@dissensoftware.com> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 07/31/2017 02:29 AM > Subject: Re: Question about VSMLIST and LSQA > Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> > > It appears that VSMLIST is documented as not returning the TCB address for > LSQA subpools because it treats all LSQA as address space level LSQA. > > One can wonder why, but it is documented. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
