No, that's a S0C6
----- Original Message -----
From: "John Melcher" <[email protected]>
To: <[email protected]>
Sent: Wednesday, January 29, 2020 9:33 PM
Subject: Re: Does S0C5 still exist ?
J <odd address> doesn't do it?
-----Original Message-----
From: IBM Mainframe Assembler List <[email protected]> On
Behalf Of Joe Dolcini
Sent: Wednesday, January 29, 2020 3:32 PM
To: [email protected]
Subject: Re: Does S0C5 still exist ?
*** External email: Verify sender before opening attachments or links ***
I thought it was leftover from MVT (non-virtual) days. I found the
following
S0C5 – Addressing Exception
Description
An address developed and used by the ABENDing program lies outside of the
available virtual storage on the processor.
Possible Causes
Indexing, Subcripting outside the program’s assigned limits.
Un-initialized index
Attempt to read an unopened input file
A missing or misspelled DD statement.
An attempt to close a dataset second time An input/output instruction is
terminated because an open is unable to complete Regarding the listed
reasons that reference datasets, I didn’t think those would get an 0c5.
On Jan 29, 2020, at 3:23 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
