The default excessive spin actions (EXSPATxx in parmlib) are SPIN ABEND TERM ACR The first action (SPIN) creates a logrec record that looks like a 071 abend, but there really isn't an abend. If the spin persists for another interval so that the ABEND action is taken, then your SLIP would match. If you want to SLIP on the first instance of excessive spin, you can you use this "undocumented, for use under direction of IBM support" procedure. Include BLWEXSNABEND06B in your TRAPS NAMES(xxxx,etc) list in DIAGxx. Then excessive spin processing will issue a 06B-4 abend for every instance of excessive spin (including the first). The abend is processed and retryed by an FRR, so no workunit actually gets abended. The purpose is just is just to allow trapping of any entry to excessive spin via SLIP C=066,RE=4 Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp. Poughkeepsie NY
"IBM Mainframe Discussion List" <[email protected]> wrote on 07/14/2021 01:05:26 PM: > From: "Binyamin Dissen" <[email protected]> > To: [email protected] > Date: 07/14/2021 04:08 PM > Subject: Why isn't a SLIP for 071 matching? > Sent by: "IBM Mainframe Discussion List" <[email protected]> > > I am having an issue with a loop and would like a SADUMP at the time of > failure (test system) > > I put in > > SLIP SET,C=071,A+WAIT,END > > but the system continues after the 071 > > Why might this happen? > > I did not see an option to WAIT should the condition occur. > > -- > Binyamin Dissen <[email protected]> > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
