Sorry
But you are right I once again failed to read documentation in regard to the
high order bit being on
REAL31
If the storage block is backed in real 31-bit or 64-bit storage, the high bit
indicator is on (one). If
the storage block is backed in real 24-bit storage, the high bit indicator is
off (zero). The low bit
and second lowest bit indicators are always off
regarding my out put from VSMLIST
the documentation says that when coding VSMLIST SP=PVT,SPACE=FREE the
allocated information block is followed by the free block
descriptor
So if block descriptor for the allocated block and I am typing this address
from screen prints that I took of the output of VSMLIST
with SP=PVT,SPACE=FREE
7F706000 0001000 00000001 7F706000 00000F28 what I do is add the
address and block length 7F706000 + 1000 this gives me
7F707000 I then add the entry or the last entry of the free block descriptor
7F7006000 + F28 = 77F06F28 this number 7F706F28 is the
starting address of the allocated storage I want to verify or VSMLOC the length
is the first total minus the second 7f707000 -
7f706f28 = D8 using this address and length I get return code 0 and tcb address
in register 1. I also realize the there can be more
than 1 free block descriptor following so I use the last
I now understand this because when VSM allocated storage it gets it in 4k
chucks the allocation starts from high to low
Whether you know it or not you helped me figure it out
Thank you
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Peter Relson
Sent: Friday, September 9, 2022 1:00 PM
To: [email protected]
Subject: Re: VSMLIST question
Joe,
You're saying that you did get output of
00000001 7FFFFF88 00001000 00000001 7FFFFFF88 00000500 within the returned data
from the VSMLIST invocation you had shown?
I can't think of a way that that would be OK. Unless I'm forgetting something,
it would be APARable and I'd encourage you to explore
that direction.
Regarding the high bit, it's documented. Specifically, "Format of Allocated
Block Descriptor" with
https://www.ibm.com/docs/en/zos/2.5.0?topic=area-allocated-storage-information<https://www.ibm.com/docs/en/zos/2.5.0?topic=area-allo
cated-storage-informationI>
You're treading dangerously, again, in the waters of providing incomplete
information.
You didn't provide complete information about your VSMLIST output, you didn't
show how you had invoked VSMLOC and with what values
when you said it didn't work, and now, with "FF7A5000", you show just the
single address. Your thought about what that is is likely
correct, but don't make us guess (the folks kindly helping out on IBM-Main,
whether IBMers, customers, or ISVs have real work to do
too). I choose not to participate in such a game.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO
IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
