As this function can never return partial pages, it will always be zero upon
first use.
To be picky, the "As" phrase of this is not quite true. IARV64 does not, but
could return a partial page, such as a partial 2G page for a smaller request
when the conditions were right (but the
Thank you Peter.
Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.
On Wed, Sep 27, 2023 at 12:34 PM Peter Relson wrote:
> Mike Shaw wrote
>
> The doc does not say what that memory object's pages contain just after
> IARV64 REQUEST=GETSTOR is issued.
>
>
> The "doc" actually does say
Mike Shaw wrote
The doc does not say what that memory object's pages contain just after
IARV64 REQUEST=GETSTOR is issued.
The "doc" actually does say so. But it's not surprising you didn't notice it,
because it's in the "guide" (and not in a section specifically for IARV64)
rather than in the
Thanks Binyamin and Ed. Clear explanations.
Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.
On Wed, Sep 27, 2023 at 3:23 AM Binyamin Dissen
wrote:
> As this function can never return partial pages, it will always be zero
> upon
> first use.
>
> On Tue, 26 Sep 2023 17:27:30 -0400 Mike
As this function can never return partial pages, it will always be zero upon
first use.
On Tue, 26 Sep 2023 17:27:30 -0400 Mike Shaw wrote:
:>Based on the IARV64 doc in the z/OS Assembler Services Guide and in the
:>z/OS Assembler Services Reference, an IARV64 REQUEST=GETSTOR should be
On 9/26/2023 2:27 PM, Mike Shaw wrote:
The doc does not say what that memory object's pages contain just after
IARV64 REQUEST=GETSTOR is issued. Does anyone on the list know?
Assuming you're referring to pageable memory, the object is completely
empty waiting for you to reference something.
Based on the IARV64 doc in the z/OS Assembler Services Guide and in the
z/OS Assembler Services Reference, an IARV64 REQUEST=GETSTOR should be
followed by an IARV64 REQUEST=DISCARDDATA,CLEAR=YES in order to be certain
that the obtained memory object contains no residual data.
The doc does not say
