If the problem occurred while a batch job was using the DSMON command (or the RACF® report writer), run the job again with a SYSABEND DD statement specified. This generates a system dump.

If an abend does not produce a system dump, and the problem is reproducible, set a SLIP trap to obtain a system dump the next time the problem recurs.

The trap set by this procedure causes an SVC dump to be generated. Generally, an SVC dump contains all the information needed for debugging RACF-related problems. You may want to re-create the problem you are investigating (or set up the conditions to allow the problem to recur) after setting the trap.

1. On the operator's console, enter this command:

   SLIP SET,COMP=xxx,ACTION=SYNCSVCD,JOBNAME=jobname,END

   where xxx is the system completion code and jobname is the job name (if a batch job is involved) or the user ID (if an interactive user is involved).
   Note: For more information about setting the SLIP trap, see z/OS MVS System Commands.
2. When the abend occurs, the system console receives message IEA989I:

   SLIP TRAP ID=nnn MATCHED

   where nnn is the system-assigned SLIP ID. The operator should notify you if a system dump was requested. You can format and read the system dump.
   Note: A system dump is not generated if the SLIP is a NODUMP SLIP.