Let's start with: there is very likely neither a "loop" nor a "spin", there is just system processing because of requested SVC Dumps.There is no "spin". If there's a loop in SDUMP you won't see more dumps being captured.
>SL SET,ID=NDMP,A=NOSVCD,LPAMOD=IEFJRASP,C=0C4 Aside from LPAMOD=IEFJRASP which in this case doesn't work because the 0C4 did not happen within IEFJRASP, it was just detected by this module. If there is continued dump processing, then the SLIP trap did not match. Skip mentioned "matchlim". That is not needed or probably even wanted for a no-dump trap (as you want the suppression no matter how often a dump is requested). Regarding DAE options: The usual way to update DAE options in general is via SET DAE=xx and the ADYSETxx parmlib member. It is possible that this dump does not overtly request DAE suppression and your DAE options do not include SUPPRESSALL. Please strongly consider using that option. We have found it very useful. The IBM Health Checker for z/OS contains CHECK(IBMDAE,DAE_SUPPRESSING) which by default looks to see if you are using SUPPRESSALL for SVC Dumps. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
