Wow! While Keith, John and Kevin here are among the few giving
correct and useful answers...
I'm dismayed by the number of responders whose "answers" are just
pulled out of their butts!
Come on Guys! You don't have to guess or speculate on something that
is so simple to look up.
I mean... why answer at all when you know you don't know???
Dave Cole
At 1/29/2020 05: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.
On Wednesday, January 29, 2020, 1:47:35 PM PST, John McKown
<[email protected]> wrote:
Cheat -- use the ABEND macro. Yes, you can use it to generate system anend
codes.
PIC 5 is basically that a physical address doesn't exist, so I doubt you
can generate it DAT on.
On Wed, Jan 29, 2020, 15:11 Melvyn Maltz <
[email protected]> wrote:
> As part of a training exercise I was challenged to write code
that abended
> S0C5
> While I'm very skilled at writing Assembler code that abends, I
failed in
> this case :-(
>
> With the advent of much more secure storage allocation (if someone
> mentions CICS Storage Violations the men in white coats will
have to sedate
> me) is it possible to create a S0C5 ?
>
> Some simple code that does it please
>
> Melvyn
At 1/29/2020 06:36 PM, Keven wrote:
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
Im probably by now the 5th or so person to respond with this answer...
