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
Joe,
You're saying that you did get output of
0001 7F88 1000 0001 7FF88 0500
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
ubtask of "yours".
>
>
> So for example I could get a block descriptor 0001 7F88 1000
> 0001 7FF88 0500now it my understanding the
> first 12 bytes is the allocated block descriptor
>
> However when I do a VSMLOC on that address I ge
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
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'
-MAIN@LISTSERV.UA.EDU
Subject: Re: VSMLIST question
Joseph
Why do you need VSMLOC at all if you are processing VSMLIST SP=PVT,SPACE=FREE ?
The TCB address is returned as part of the answer area buffer prior to each set
of ALLOC+FREE descriptors for each subpool.
It looks something like
> On Sep 7, 2022, at 10:59 AM, Rob Scott wrote:
>
> Joseph
>
> Why do you need VSMLOC at all if you are processing VSMLIST SP=PVT,SPACE=FREE
> ?
>
> The TCB address is returned as part of the answer area buffer prior to each
> set of ALLOC+FREE descriptors for
Joseph
Why do you need VSMLOC at all if you are processing VSMLIST SP=PVT,SPACE=FREE ?
The TCB address is returned as part of the answer area buffer prior to each set
of ALLOC+FREE descriptors for each subpool.
It looks something like this :
# of TCBs
TCB_STRUCT(1
Rob
You are correct 7FF……. Are LSQA type address
However my question is using VSMLIST SPACE=FREE SP=PVT the returned block
descriptors are both allocated followed by the free
Should I not be able to obtain the owning TCB
With VSMLOC for the allocated block ?
Thanks
> On Sep 7, 2
Joseph,
The example address you posted looks very much like LSQA to me - are you sure
it was returned by VSMLIST SP=PVT ?
Also - did you check the return code from VSMLOC?
Might be worth capturing a in-flight dump of the target address space and
comparing what you are seeing with IPCS VSMDATA
Hi
Its my understanding that when code the following (below the code for VSMLIST)
what gets returned in my work area is the both an
allocated followed by free storage this is what on understand from bullet 4
specified in the authorized Assembler guide page 240
So for example I could
ALLOC means GETMAIN/STORAGE OBTAIN
I mean I understand that z/os always gets in increments of 1K or 4096 so free
means it was part of the storage z/os obtained but the user didn’t request so
the storage that the user requested really starts at 7FF9CE28 right ?
> On Jul 21, 2022, at 10:28 AM,
>From MVS Authorized Assembler Services Reference:
,SPACE=ALLOC
,SPACE=FREE
,SPACE=UNALLOC
Specifies whether allocated, allocated and free, or unallocated storage is to
be reported.
ALLOC indicates that the virtual addresses and lengths of blocks of storage
allocated to the specific
area are to
The following is a layout for VSMLIST SP=PVT,SPACE=FREE
It is my understanding that with SPACE=FREE the free space entry is listed
and then the allocated ?
So for the following entry
Starting with the subpool descriptor, then TCB then number of free blocks
then free block address and free
When issuing VSMLIST SP=PVT,SPACE=FREE
If the entire block is not allocated, then with space=free 2 block
descriptor are mapped 1) the first and 2) free
My reason for posting is my question the first block descriptor is that
total or allocated the documentation says allocated
My second
So the allocated storage would be whitin 51000 bytes meaning the range of
storage is 7FF9C000 - 7FFED000 and the ALLOC starts at 7FFEC1D8 do I have it
right ?
> On Feb 14, 2022, at 10:12 AM, Harris Morgenstern wrote:
>
> From MVS Authorized Assembler Services Ref:
>
> ,SPACE=ALLOC
>
>From MVS Authorized Assembler Services Ref:
,SPACE=ALLOC
,SPACE=FREE
,SPACE=UNALLOC
Specifies whether allocated, allocated and free, or unallocated storage is
to be reported.
ALLOC indicates that the virtual addresses and lengths of blocks of
storage allocated to the specific
area are to be
Hi
On VSMLIST SP=PVT,SPACE=FREE
In the following block descriptor
... 0001 7FF9C000 00051000
0001 7FF9C000 0E28
The first block descriptor at address at address 7FF9C000 for length of
51000 IS FREE allocated storage starts at 7FF9C000 + 51000 or 7FFED000
I'm hoping to use the VSMLIST service in a PC-ss routine running in
primary mode to get the unallocated private areas of the secondary address
space. Is this possible, or will the call below just give me the private
areas of the primary?
Unfortunately, you will have to consider your hope
I'm hoping to use the VSMLIST service in a PC-ss routine running in primary
mode to get the unallocated private areas of the secondary address space. Is
this possible, or will the call below just give me the private areas of the
primary?
Thanks
Steve
VSMLIST SP=PVT,WKAREA=((R2),(R3)),SPACE
The convention for the past 15 years or so has been first two letters of
first name and first four letters of last name. So you'd probably be
sts...@sas.com. For collisions, I think it goes to three and three, so
possibly ste...@sas.com. You could always try to bribe somebody to be
sas...@sas.com
I asked the question based on the Auth. Ass. Services Guide... later on, I
looked at the Diagnosis Ref., which says that the 230s are allocated in the
250s. Ah well, it was only idle curiosity anyway.
If I got a job with SAS, would my email be s...@sas.com? Or sas...@sas.com?
UGH. Better stay
In article
you wrote:
> In sorting through the Rubik's Cube that is the subpool selection charts,
> it appears to me that 233-235 are defined exactly the same as 253-255
> respectively. Is there some difference I'm missing?
>
In sorting through the Rubik's Cube that is the subpool selection charts,
it appears to me that 233-235 are defined exactly the same as 253-255
respectively. Is there some difference I'm missing?
sas
--
For IBM-MAIN subscribe /
>>A key reason for the last is so that someone can use LSQA for an SRB
that
>>is not associated with a TCB, for which you might not want private
storage
>>obtained by the SRB to be freed just because some task terminates.
>Seems like a weak reason. Are there other ways SRBs are protected from
On Mon, 31 Jul 2017 10:52:15 -0400 Peter Relson <rel...@us.ibm.com> wrote:
:>>>Since LSQA is System Private Storage how come there isn't a TCB
:>associated
:>>>with it
:>>Who said there isn't?
:>VSM said so.
Because VSMLIST is not examining the correct
rminates.
I do not know whether the task association for subpools 253 and 254 is
surfaced by VSMLIST.
Peter Relson
z/OS Core Technology Design
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
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
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 <reichman...@gmail.com> wrote:
:>Sorry Binyamin
:&
-MAIN@LISTSERV.UA.EDU
Subject: Re: Question about VSMLIST and LSQA
On Sat, 29 Jul 2017 21:48:24 -0400 Joe Reichman <reichman...@gmail.com>
wrote:
:>Since LSQA is System Private Storage how come there isn't a TCB associated
:>with it
Who said there isn't?
--
Binyamin
Hi
Since LSQA is System Private Storage how come there isn't a TCB associated
with it
thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
On Sat, 29 Jul 2017 21:48:24 -0400 Joe Reichman wrote:
:>Since LSQA is System Private Storage how come there isn't a TCB associated
:>with it
Who said there isn't?
--
Binyamin Dissen
http://www.dissensoftware.com
Director, Dissen Software,
Hi
Since LSQA is System Private Storage how come there isn't a TCB associated
with it
thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
On 22 February 2017 at 11:16, Joseph Reichman wrote:
> I know if you specify GSPV or SHPSV on the attach tasks can Share ? A subpool
> If this is not specified on the attach would a subtask get a S0C4 for
> referencing storage
> Obtained by the originating task
Use of
On 2/22/2017 10:15 AM, Joseph Reichman wrote:
I know if you specify GSPV or SHPSV on the attach tasks can Share ? A subpool
If this is not specified on the attach would a subtask get a S0C4 for
referencing storage
Obtained by the originating task
No.
A subpool is a logical grouping of
ERV.UA.EDU
Subject: Re: VSMLIST
Greg
Thanks for your clarification on this note Can I ask one more related question
I know if you specify GSPV or SHPSV on the attach tasks can Share ? A subpool
If this is not specified on the attach would a subtask get a S0C4 for
referencing storag
paged out I would get a S0C4 pic 11
>>
>> If VSMLIST determines it has been getmain'ed
>>
>> Maybe I can PGSER FIX back in
>>
>> I just got 2.2 via RD they (IBM) gave us Omegamon maybe that would point
>> me to the type of storage that I'm looking to drive my code
On 2/22/2017 7:17 AM, Joseph Reichman wrote:
I am trying to reference storage that I ( my TCB didn't necessarily obtain )
Sometime I think if this storage has been paged out I would get a S0C4 pic 11
If VSMLIST determines it has been getmain'ed
Maybe I can PGSER FIX back in
I just got 2.2
I am trying to reference storage that I ( my TCB didn't necessarily obtain )
Sometime I think if this storage has been paged out I would get a S0C4 pic 11
If VSMLIST determines it has been getmain'ed
Maybe I can PGSER FIX back in
I just got 2.2 via RD they (IBM) gave us Omegamon maybe
Tony Harminc wrote:
>So why do you want to know that a page is GETMAINed and paged out? What will
>you do differently if your program finds this out? There are other
>possibilities; a page can be accessible but not GETMAINed.
>VSMLIST can tell you if a page is GETMAINED, and LRA
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Joe Reichman
Sent: Tuesday, February 21, 2017 6:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: VSMLIST
I am Looking for Storage that was GetMain'ed and Page'ed out
-Original Message-
From: IBM Mainframe Discussion List [
GETMAINed.
VSMLIST can tell you if a page is GETMAINED, and LRA[G] can tell you
if it's paged in or out, but those things can change the moment you
look away, or even as you are looking, in a multiprocessor
environment. Unless you are running disabled or hold locks that you
probably shouldn't be holdi
I am Looking for Storage that was GetMain'ed and Page'ed out
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Jim Mulder
Sent: Tuesday, February 21, 2017 4:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: VSMLIST
> I'm trying to f
> I'm trying to find data for PGSER FIX
>
> would VSMLIST. For free space give me address of storage that have
> been allocated but paged out
No, VSM (and hence VSMLIST) knows nothing about if or
where any virtual storage is backed.
Jim Mulder z/OS Diagnosis, Design, Developmen
Hi
I'm trying to find data for PGSER FIX
would VSMLIST. For free space give me address of storage that have been
allocated but paged out
Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
44 matches
Mail list logo