I’ve developed code that executed LURA and STURA instructions and I saw
a few S0C5s along the way. I remember thinking at the time that I had finally
filled in my S0Cx card (I.e., I had at that point written code that had
non-deliberately ABENDed with a S0C1 through S0C9. I might even have cracked a
beer that evening to mark the event.I think S0C5 only results from an attempt
to access real storage addresses outside the available range
I’m probably by now the 5th or so person to respond with this answer...
On Wed, Jan 29, 2020 at 5:01 PM -0600, "Steve Smith" <[email protected]> wrote:
I think that's the winner! Much easier than stepping into DAT-off on one's
own (unless you happen to actually still have a V=R region).
John McKown's suggestion is nice for runner-up.
sas
On Wed, Jan 29, 2020 at 5:12 PM Keith Moe wrote:
> Yes. It is still possible to generate a REAL 0C5 (Addressing Exception)
> abend. To do so, you must be in DAT OFF mode. z/OS has DAT OFF Services and
> until you have a full 64-bit addressable real storage, an 0C5 can occur.
>
> Back in 2005, I accidentally generated one in a DAT OFF service call.
>
> Keith Moe
> BMC Software, Inc.
