DUMP
Use DUMP
to produce a system dump at
compile time for an internal compiler error.
Default is: NODUMP
Abbreviations
are: DU
| NODU
Not for
general use: The DUMP
option should be used only
at the request of an IBM® representative.
The dump, which consists of a listing of the compiler's registers and a storage dump, is intended primarily for diagnostic personnel for determining errors in the compiler.
If you use the DUMP
option,
include a DD
statement at compile time to define SYSABEND
, SYSUDUMP
,
or SYSMDUMP
.
With DUMP
, the
compiler will not issue a diagnostic message before abnormal termination
processing. Instead, a user abend will be issued with an IGYppnnnn message.
In general, a message IGYppnnnn corresponds to
a compile-time user abend nnnn. However, both IGYpp5nnn and
IGYpp1nnn messages produce a
user abend of 1nnn. You can usually distinguish
whether the message is really a 5nnn or a 1nnn by
recompiling with the NODUMP
option.
Use NODUMP
if
you want normal termination processing, including:
- Diagnostic messages produced so far in compilation.
- A description of the error.
- The name of the compiler phase currently executing.
- The line number of the COBOL statement being processed when the
error was found. (If you compiled with
OPTIMIZE(1|2)
, the line number might not always be correct; for some errors, it will be the last line in the program.) - The contents of the general purpose registers.
Using the DUMP
and OPTIMIZE(1|2)
compiler options
together could cause the compiler to produce a system dump instead
of the following optimizer message:
"IGYOP3124-W This statement may cause a program exception at
execution time."
This situation does not represent a compiler error.
Using the NODUMP
option will allow the compiler to
issue message IGYOP3124-W and continue processing.
Language Environment® Debugging Guide (Understanding abend codes)