z/OS Communications Server: IP Diagnosis Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Dumps

z/OS Communications Server: IP Diagnosis Guide
GC27-3652-02

Table 1 describes the types of available dumps.
Table 1. Description of dumps
Type of dump Description
ABEND dumps Use an ABEND dump when ending an authorized program or a problem program because of an uncorrectable error. These dumps show:
  • The virtual storage for the program requesting the dump.
  • System data associated with the program.
The system can produce three types of ABEND dumps— SYSABEND, SYSMDUMP, and SYSUDUMP. Each one dumps different areas. Select the dump that gives the areas needed for diagnosing your problem. The IBM-supplied defaults for each dump are:
  • SYSABEND dumps. The largest of the ABEND dumps, containing a summary dump for the failing program plus many other areas useful for analyzing processing in the failing program.
  • SYSMDUMP dumps. Contains a summary dump for the failing program, plus some system data for the failing task. In most cases, SYSMDUMP dumps are recommended, because they are the only ABEND dumps that are formatted with IPCS.
  • SYSUDUMP dumps. The smallest of the ABEND dumps, containing only data and areas about the failing program.

See z/OS MVS Diagnosis: Tools and Service Aids for more information about ABEND.
SVC dumps SVC dumps can be used in two different ways:
  • Most commonly, a system component requests an SVC dump when an unexpected system error occurs, but the system can continue processing.
  • An authorized program or the operator can also request an SVC dump when diagnostic data is needed to solve a problem.
SVC dumps contain a summary dump, control blocks, and other system code, but the exact areas dumped depend on whether the dump was requested by a macro, command, or SLIP trap. SVC dumps can be analyzed using IPCS.

See z/OS MVS Diagnosis: Tools and Service Aids for detailed information.

If a console dump or SLIP is requested:
  • Capture the OMVS and (if applicable) affected application address spaces as well as TCP/IP.
  • SDATA specification should contain the RGN, TRT, PSA, SUM, CSA and SQA keywords (at minimum).
FFST dumps
FFST™ dumps fall into two categories: SDUMPs (full dumps) and FFST minidumps (partial dumps). The type of dump produced depends on the characteristics of the probe that produced it.
  • FFST uses the operating system SDUMP macroinstruction to provide a full dump of the address space where the problem occurred.
  • If the SDUMP option has not been coded for the probe triggering the dump, an FFST minidump is written to the output data set. The probe output data for the TCP/IP minidumps are found in data sets that were allocated when FFST was installed.
Stand-alone dumps Use a stand-alone dump when:
  • The system stops processing.
  • The system enters a wait state with or without a wait state code.
  • The system enters an instruction loop.
  • The system is processing slowly.

These dumps show central storage and some paged-out virtual storage occupied by the system or stand-alone dump program that failed. Stand-alone dumps can be analyzed using IPCS.

See Analyzing loops for detailed information.
Parent topic: Overview of available tools and service aids

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014