Well ....
IGV007I 08.26.33 DIAG DISPLAY 430
VSM TRACK CSA(ON) SQA(ON)
VSM TRACE GET(OFF) FREE(OFF)
VSM ALLOWUSERKEYCSA(NO)
VSM BESTFITCSA(NO)
VSM USEZOSV1R9RULES(YES)
TRAPS NAME(BLWEXSNABEND06B)
CBLOC
VIRTUAL24()
VIRTUAL31()
REAL31()
REAL64()
REUSASID(YES)
ALLOWUSERKEYCADS(NO)
AUTOIPL SADMP(NONE) MVS(NONE)
FREEMAINEDFRAMES(YES)
FF31HIGH(YES)
ASLR(NO)
IEE735I 08.27.13 SLIP DISPLAY 432
ID=0002,NONPER,ENABLED
ACTION=WAIT,SET BY CONS ********,RBLEVEL=ERROR,MATCHLIM=2,0
COMP=06B,REASON=4
IEE178I AUTOMATIC RECOVERY IS IN PROGRESS 064
NO OPERATOR ACTION IS REQUIRED.
PROCESSOR (0001) DETECTED AN EXCESSIVE DISABLED SPIN LOOP
WAITING FOR RISGNL RESPONSE FROM PROCESSOR (0000).
AUTOMATIC RECOVERY ACTION IS SPIN
IEE178I AUTOMATIC RECOVERY IS IN PROGRESS 065
NO OPERATOR ACTION IS REQUIRED.
PROCESSOR (0001) DETECTED AN EXCESSIVE DISABLED SPIN LOOP
WAITING FOR RISGNL RESPONSE FROM PROCESSOR (0000).
AUTOMATIC RECOVERY ACTION IS ABEND
Trap did not hit.
On Wed, 14 Jul 2021 16:36:31 -0400 Jim Mulder <[email protected]> wrote:
:> 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
--
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
