Joe R wrote: <snip> Let me use an example 00000001 00007000 000001000 00000001 00007000 00000800
So the allocated address is 7800 for 200 </snip> Close. The freed storage starts at 7000 and runs for 800. That means that allocated storage starts at 7800 and runs for 800. If you showed more data that preceded this, you'd have the owning TCB address. Keep in mind that subpool 0 can be shared across tasks. The owning task might not be "yours" or a subtask of "yours". <snip> So for example I could get a block descriptor 00000001 7FFFFF88 00001000 00000001 7FFFFFF88 00000500 now it my understanding the first 12 bytes is the allocated block descriptor However when I do a VSMLOC on that address I get nothing return in the TCB= field </snip> This clearly is not real data from the VSMLIST that has been shown. Why did you have to make up data? There cannot possibly be a x'1000' byte block starting at 7FFFFF88 even if the 7FFFF000 page wasn't ineligible. 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
