Dump information is only written to CEEDUMP following an S0C1 abend,
if the S0C1 was handled by LE. This should be the normal case in a LE
environment.
But in this case, if you don't get CEEDUMP information written following
the
S0C1, I guess that THIS S0C1 is not handled by LE, but it is a normal S0C1
handled by the system, so the normal action is: output to SYSUDUMP, if
SYSUDUMP is present in the Job Step, and no output, if not. The opsys
does not output anything to CEEDUMP.
The reason why the S0C1 is not handled by LE could be:
NOSPIE,NOSTAE option in effect, via LE parm or via CEEOPTS
(don't know, there are several possibilities to do this) ... this is
called TRAP(OFF)
nowadays, I guess ...
the S0C1 occurs, BEFORE the LE error handler has been established
other reasons ... ???
HTH
kind regards
Bernd
Am 24.11.2014 22:38, schrieb Peter Ten Eyck:
I have a COBOL program that is getting a SOC1 and produces a dump when the
SYSUDUMP DD is code in the failing step. If CEEDUMP is coded instead of
SYSUDUMP no dump is produced.
This program is complied with the same COBOL parameters and run in the same LE
environment as other COBOL programs which do produce a dump when using the
CEEDUMP DD.
Is there something about SOC1 abends that would cause the issues with CEEDUMP?
What am I missing here?
Note:
z/OS 1.13
IBM ENTERPRISE COBOL FOR Z/OS 4.2.0
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
