I am speculating some, but it seems to me that a S0C5 would be impossible with DAT-on unless somebody screwed up the DAT tables. If you get into real mode, then it should be possible to generate an addressing exception easily enough. Whether z/OS would turn that into a S0C5 nowadays is debatable, as I'd think it would find your program's behavior very odd; so it may have instituted new penalties.
sas On Wed, Jan 29, 2020 at 4:22 PM Steve Thompson <[email protected]> wrote: > Get the PoOP and look at Program Interrupt Code (PIC) 5. > > I can't remember off the top of my head if this is addressing or > specification exception. > > Regards, > Steve Thompson > > On 1/29/20 4:11 PM, Melvyn Maltz 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 > > > -- sas
