Troubleshooting › Common Troubleshooting Procedures › Abends Occurring

Abends Occurring

Symptom:

Abends are being generated.

Solution:

Do the following:

• Provide a system dump COPY from the dump data set onto a 6250 BPI magnetic tape or cartridge. Sample JCL, is shown below:

  //DUMP          JOB
  //              EXEC            PGM=IEBGENER
  //SYSPRINT      DD              SYSOUT=*
  //SYSIN         DD              DUMMY
  //SYSUT1        DD              DISP=SHR,DSN=SYS1.DUMPxx
  //SYSUT2        DD              DISP=(,KEEP),UNIT=TAPE,DSN=xxx
  

• Provide all copies of the system log data from 15 minutes before and 5 minutes after the abend occurred. Hardcopy is preferred. Include the issue number in the subject field.
• If the abend was produced by a batch job, provide a copy of the JCL for that batch job and the JES joblog.
• If TSS message TSS9999E indicated the abend, record the text of the message, including all register and offset information which follow the message.
• Copy all other CA Top Secret messages that appear with the job or session in the order in which they occur.

Most CA Top Secret abend messages and dump titles contain and document the abend code, program name, and program offset associated with the error. When an CA Top Secret dump exists in a SYS1.DUMPxx data set, the z/OS operator command “D D,E” can be used to gather further details about the error. Similarly, when an CA Top Secret dump is being viewed via IPCS, the “ST FAILDATA IPCS command can now be used to obtain a summary of the error. Whenever possible provide “ST FAILDATA” (or “D D,E”) output to CA when reporting an abend.