SLIP behaves differently for a program check converted to an ABEND. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Steve Thompson <[email protected]> Sent: Monday, April 22, 2024 10:24 AM To: [email protected] Subject: Re: S0c4 creation IN line with what was said, you can force it by issuing ABEND (or related) and telling it what ABEND you want. You can also EX an EX and get a S0C3. I've never seen that ABEND by accident (e.g., wild branch into data). And no co-workers I've had (all of us doing ALC based development) have ever seen that one by accident. Steve Thompson On 4/21/2024 7:39 AM, Bernd Oppolzer wrote: > I'd suggest to be very careful with such codings; > a co-worker some years ago did this and - by accident - the > code ran privileged, > which caused the whole LPAR to hang. > > Same goes for ST at address zero, which was suggested by > another poster. > > Maybe it would be better to write protect your own module and > try to write > into your own static CSECT. This would not put other jobs in > your system in danger. > > Or: do your SLIP trap experiments with another sort of ABEND. > > Kind regards > > Bernd > > > Am 21.04.2024 um 11:21 schrieb Rupert Reynolds: >> If it's your STC, then include something dirty like >> >> BANG NC 16(4,R0),16(R0) AND CVT pointer with >> itself--should fail >> >> although I should say that might raise eyebrows on a >> production system ;-) >> >> Roops >> >> On Sun, 21 Apr 2024, 08:45 Peter, < >> [email protected]> wrote: >> >>> Hello >>> >>> Good morning >>> >>> Is there any sample Jobs or I can enforce a s0c4 abend in a >>> Started task ? >>> >>> I am trying to teach SLIP trap to a rookie..Is there any >>> other efficient >>> way to do this? >>> >>> Peter >>> >>> ---------------------------------------------------------------------- >>> >>> 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
