They say that the memory is the second thing to fail. OS/VS, including MVS, reflects 004 as S0C$ and 005 as S0C%, although the latter is rare on OS/VS systems. However, OS/VS also reflects some other codes as S0C4, e.g., reference to an unallocated page.
By the time you get to z/OS there are a lot more fingers in the pie. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of Paul Gilmartin [[email protected]] Sent: Wednesday, April 27, 2022 4:19 PM To: [email protected] Subject: Re: EXTERNAL: CIBXUTOK fetch protected On Wed, 27 Apr 2022 13:48:12 -0400, Steve Smith wrote: >Well, S0C4-11 does not mean the storage is fetch-protected. It means the >virtual address doesn't exist. .. > In SA22-7871-10 z/Architecture IBM Reference Summary I read: Program-Interruption Codes At real-storage locations 142-143 (8E-8F hex) Code Instr. (Hex) Condition ILC Set Ending 0001 Operation exception 1 2 3 S 0002 Privileged-operation exception 2 3 S 0003 Execute exception 2 3 S 0004 Protection exception 1 2 3 S T 0005 Addressing exception 1 2 3 S T ... A Historian told me long ago that Addressing exceptions were so rare before DAT that MVS/XA elected to reflect 0005 as S0C4 for compatibility with existing code. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
