Abstract for MVS Dump Output Messages

Purpose of this information

This information describes the messages issued by components of z/OS. The messages can appear in:

SVC dumps, stand-alone dumps, or SYSMDUMP ABEND dumps formatted by the interactive problem control system (IPCS)
Trace data sets formatted by the interactive problem control system (IPCS)
ABEND dumps or SNAP dumps produced by the dumping services

In dump or trace data sets formatted by IPCS, the messages appear interactively on a terminal or in a printed dump.

Who should read this information

This information is for anyone who analyzes or formats dump or trace data sets. Usually this person is a system programmer.

How to use this information

The messages are in topics that are arranged alphabetically by the message prefixes. In each topic, the messages are arranged numerically by the numbers following the prefix. The description for each message:

Explains why the system issued the message
Identifies the component, subsystem, or product issuing the message
Describes the actions taken by the system
Suggests appropriate responses to the message

A small number of messages indicate a problem in the dumping or formatting process. For these, the system programmer response assumes that the programmer has performed the customary diagnosis described in the z/OS Problem Management.

This information also includes unnumbered messages, which are issued by the auxiliary storage manager (ASM) and virtual storage management (VSM) components.

Where to find more information

Many message descriptions refer to:

Data areas and control blocks: Visit z/OS® Internet Library at z/OS Internet library for z/OS MVS Data Areas manuals.
Dumps: For examples of ABEND, stand-alone, and SVC dumps and how to read them, see z/OS MVS Diagnosis: Tools and Service Aids. For examples of component output from dumps and how to read and request it, see z/OS MVS Diagnosis: Reference.
Identification of a component, subsystem, or product: See the z/OS MVS Diagnosis: Reference to identify the component, subsystem, or product from the name of an IBM® module or for a macro. The module prefix and macro tables give the program identifier to be used in a PIDS symptom in a search argument.
Messages: See
System completion and wait state codes: See z/OS MVS System Codes.
Logrec data set error records: For information about reading the formatted software records, see z/OS MVS Diagnosis: Reference.
Trace output: For the formats and the meaning of the information in the generalized trace facility (GTF) trace, component trace, instruction address trace, master trace, and system trace, see z/OS MVS Diagnosis: Tools and Service Aids.
User completion codes: See the IPCS topic in z/OS MVS Diagnosis: Reference for the 4-digit decimal user completion codes produced by IPCS.

For the titles and order numbers of other documents referenced in this information, see z/OS Information Roadmap.