Peter,
Thanks for the help.
When I did a display of the X'8000' area above-the-bar, I was only
seeing the first 8K X'2000'.
I ran through the memory right after the IARST64 accessing each 8K. No
abends. When I browsed the memory in IPCS, I saw the entire X'8000'.
I conclude that if
sion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Relson
Sent: Wednesday, April 22, 2020 8:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IARST64 problem
The example as posted would not even assemble with default assembly
options, so this is a bit confusing.
I refer to the lower case
The example as posted would not even assemble with default assembly
options, so this is a bit confusing.
I refer to the lower case operands such as "yes" for sysstate amode64=yes.
Maybe there's use of some assembly COMPAT option?
There are also possibilities that the switch from amode 31 to
" RDP 2009
-Message d'origine-
De : IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] De la part
de Pierre Fichaud
Envoyé : mercredi 22 avril 2020 01:20
À : IBM-MAIN@LISTSERV.UA.EDU
Objet : IARST64 problem
I've used IARV64 and IARCP64 extensively. This is my first t
,SIZE=sizeWhen REQUEST=GET is specified, a required input parameter that
indicates the size of the storage to be obtained. The size can be anywhere
between 1 and [image: Start of change]128K[image: End of change] bytes. The
size is rounded up to a power of 2. So cell sizes are 64, 128, 256, 512,
I've used IARV64 and IARCP64 extensively. This is my first time trying IARST64.
Forgive the staggering after the cut and paste.
dsa_word contains X'8000'
. 169800 str00,dsa_word
Save the size in bytes .
.
