In OS/360 based systems there are 4 types of storage dumps after an abnormal program termination all users have accessed to.
- LE (Language Environment) dumps. These are generally printed, and show basic Language Environment information.
- Summary dumps
A summary dump is presented to a user in the JESMSGLG data set. You generally see the registers, the location of the last instruction executed, sometimes formatted to show the load module and offset in the load module where the instruction is located, though this information is often incorrect and 12 bytes of storage, from 6 bytes before the location counter to 6 bytes after the location counter.
- SYSUDUMP/SYSABEND dumps.
These dumps are printed dumps. The terms SYSUDUMP and SYSABEND refer to the DD statement on which the dumps are printed. Both dumps display many system control blocks related to the user's address space. In my opinion the usefulness of the control block portion of the dump has been negated by formatting many control block that do not appear to be relevant to the problem. Both dumps show storage. Historically, a SYSUDUMP dump displayed all allocated user storage, and SYSABEND dumps displayed some system storage in addition to the allocated user storage. In MVS systems the contents of these dumps are controlled by system options set by the systems programmers, so the contents of the dumps may not be the same as earlier systems. In most places SYSUDUMP dumps stay reasonably true to the traditional model, but SYSABEND dumps are often the same as SYSUDUMP dumps.
A SYSMDUMP dump is unformatted binary data directed to a data set specified by the SYSMDUMP DD statement rather than printed. You must use a program called IPCS to process these dumps, either interactively at a TSO session, or by running TSO in batch to produce printed reports. Using IPCS effectively requires considerable knowledge of IPCS and the system. Once you have learned IPCS it is usually easier to dig out relevant data than by trying to dig through a printed dump.
Now I have talked about using the SYSUDUMP, SYSABEND and SYSMDUMP DD statements to determine the type of dump. If more than one of these DD statements is present, the system uses the last DD statement for the job step. See the "MVS JCL Reference" manual for your z/OS release.