>SUBPOOL 230 KEY 05 OWNED BY TCB 008FF050 > ADDRESS 008C4000 LENGTH 00001000 > FREE AREA 008C4000 LENGTH 00000060 > FREE AREA 008C40B8 LENGTH 00000F48 > ADDRESS 008C5000 LENGTH 00001000 > FREE AREA 008C5000 LENGTH 00000030 > FREE AREA 008C50B8 LENGTH 00000F48
>What is it telling me by having multiple addresses and multiple free >areas? Or maybe another question would be what caused that? I know it >isn't just accounting for each 4k because sometimes the address length >portion is multiples of 4k. I'm not sure what the real question is. It is accounting for "every 4K" but not necessarily on "each individual 4K". The system has differing structures for different areas of storage. This is simply showing you according to the area that the system chooses to be managing. Each of the above is saying that the area starting at address x for length y is partially allocated. The parts not shown as "free area" are allocated. The simplest case would be that there were some two getmains (or storage obtains) and subsequently a freemain. For example, a getmain of x'F48' followed by a getmain for x'58' followed by a freemain for x'F48' could result in the pattern shown for 08C4000 / 1000. Based on various criteria, an allocation may be satsified from the "end of a page" or the "beginning of a page" when no sub-page area is available. Why do you truly care? Usually, VSMLIST is used to check, for a particular address, is it allocated or free. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
