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. On Sun, 30 Jul 2017 09:37:53 -0400 Joe Reichman <[email protected]> wrote: :>Sorry Binyamin :> :>Didn't see your reply the VSM Descriptor when looking for LSQA allocated has :>zeros for the TCB field :> :>thanks :> :>-----Original Message----- :>From: IBM Mainframe Discussion List [mailto:[email protected]] On :>Behalf Of Binyamin Dissen :>Sent: Sunday, July 30, 2017 2:53 AM :>To: [email protected] :>Subject: Re: Question about VSMLIST and LSQA :> :>On Sat, 29 Jul 2017 21:48:24 -0400 Joe Reichman <[email protected]> :>wrote: :> :>:>Since LSQA is System Private Storage how come there isn't a TCB associated :>:>with it :> :>Who said there isn't? -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
