Am 22.11.2019 um 23:23 schrieb Paul Gilmartin:
Do I understand correctly that enforcement is entirely by
software; those addresses are quite acceptable to the hardware?
the translation of the virtual addresses to real addresses is not done
by software only; there is some hardware support.
The “dead zone” is an OS-specific restriction. Processes running under
Linux on z/Architecture see the whole 64-bit address space, for example.
Keven
On Fri, Nov 22, 2019 at 4:23 PM -0600, "Paul Gilmartin"
On 2019-11-22, at 08:14:13, Dougie Lawson wrote:
>
> ABEND0C4 PIC38 is the fun one. You can't step into any 32-bit address as
> the 32nd bit was reserved by the MVS to MVS/XA change to mark whether we
> were in 24-bit or 31-bit.
>
> So the 64-bit guys decided that the easiest fix was to
On Fri, 22 Nov 2019 15:14:13 +, Dougie Lawson wrote:
>ABEND0C4 PIC38 is the fun one. You can't step into any 32-bit address as
>the 32nd bit was reserved by the MVS to MVS/XA change to mark whether we
>were in 24-bit or 31-bit.
>
>So the 64-bit guys decided that the easiest fix was to
The original "dead zone" was x'8000 ' to x' '. I think I
remember my first IARVx giving me address x' 0001 ', but that
was long ago. This has been expanded up to the 32gb uh... border (x'
0008 ') some years ago. Rumor is Java uses this area to have 32gb
of
ABEND0C4 PIC38 is the fun one. You can't step into any 32-bit address as
the 32nd bit was reserved by the MVS to MVS/XA change to mark whether we
were in 24-bit or 31-bit.
So the 64-bit guys decided that the easiest fix was to completely disallow
any address from 800 through to 8FFF,
My mistake was jumping the gun and not looking at the reason code
It clearly stated that S0C4 Reason code 38
Had to do with AMODE 64 when the high order bit of a 31 bit pointer ( which is
not part of the address in amode 31 but is in amode 64 ) it is best practice to
do a LLGTR RX before
I continue not to understand why you repeatedly fail to provide the
information necessary for the good folks on this list to help you.
So I have LOAD a module amode 64 rmode 24
Your module does not need to match the RMODE of your DCB unless your DCB
is physically resident in the module,
I understand haven’t program that much in amode 64
Thanks
Joe Reichman
170-10 73 rd ave
Fresh meadows NY 11366
> On Nov 22, 2019, at 5:50 AM, Jonathan Scott
> wrote:
>
> Ref: Your note of Thu, 21 Nov 2019 22:26:07 -0500
>
> BASR doesn't switch AMODE. If you want to switch AMODE you
Ref: Your note of Thu, 21 Nov 2019 22:26:07 -0500
BASR doesn't switch AMODE. If you want to switch AMODE you need
to use BASSM (and return using BSM, as the return address will
be odd for AMODE 64).
If you BASR staying in AMODE 64, the high word of the register
needs to be zero. If you're not
Or maybe a question instead of a musing?
Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.
On Fri, Nov 22, 2019, 1:00 AM Keven wrote:
>
>
>
>
> The paucity of detail makes answering your inquiry a matter of
> inductive supposition. Maybe you should post additional information
11 matches
Mail list logo
