No, if we're going to be pedantic it should be 'PIC 0001 is *NOT* "S0C1 in Z/OS-speak" (sic)', i.e., quote the text as written but indicate that the spelling error was in the original.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Charles Mills <[email protected]> Sent: Thursday, January 30, 2020 2:32 PM To: [email protected] Subject: Re: Does S0C5 still exist ? z/OS with a lower case z, if we're going to be pedantic here. CharlesSent from a mobile; please excuse the brevity. -------- Original message --------From: Seymour J Metz <[email protected]> Date: 1/30/20 11:19 AM (GMT-08:00) To: [email protected] Subject: Re: Does S0C5 still exist ? PIC 0001 is *NOT* "S0C1 in Z/OS-speak"; ABEND S0001 is what you get *ONLY* if you choose not to handle PIC 0001 yourself.There will be PIE in the skie by and by - it's a SPIE!--Shmuel (Seymour J.) Metzhttp://mason.gmu.edu/~smetz3________________________________________From: IBM Mainframe Assembler List <[email protected]> on behalf of Dan Greiner <[email protected]>Sent: Thursday, January 30, 2020 12:25 PMTo: [email protected]: Re: Does S0C5 still exist ?There are numerous means of generating a guaranteed program exception, but Mr. McKown's technique of jumping to the second halfword of the relative branch is clever.However, if you are depending on seeing an operation exception (program-interruption code 0001, or S0C1 in Z/OS-speak), there's one situation where you could be disappointed: If the program is executing on a z14 or later, and the instruction-execution-protection (IEP) facility is active and applicable, you will get a protection exception (PIC 0004). See page 3-14 of the latest PoO for details on IEP.
