- ABEND Dump
- 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. SYSMDUMP dumps are the only ABEND dumps
that you can format with IPCS
- SYSUDUMP dumps
- The smallest of the ABEND dumps, containing data and
areas only about the failing program.
- SNAP Dump
- Use a SNAP dump when testing a problem program. A SNAP
dump shows one or more areas of virtual storage that a program, while running,
requests the system to dump. A series of SNAP dumps can show an area at
different stages in order to picture a program's processing, dumping one or
more fields repeatedly to let the programmer check intermediate steps in
calculations. SNAP dumps are preformatted, you cannot use IPCS to format
them.
- Note that a SNAP dump is written while a program runs,
rather than during abnormal end.
- Stand-Alone Dump
- 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-alonedump program that failed.
Stand-alone dumps can be analyzed using IPCS.
IBM
manual for Stand-Alone Dump
- 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 they need diagnostic data 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 panels.
Looks like we use an older BLSCECT member in our
SYS1.ParmLib. Can sombody confirm if this cause the problem?
Yes, it will... along with downlevel copies of a number of
other PARMLIB members that BLSCECT includes. You must have the PARMLIB levels
that match the load modules in MIGLIB
Greg Dyck
z/OS Core Technology Design
IBM-Main
Discussion Group |