As I told already in my previous post on this topic:
there are certains types of errors, especially when code area is overwritten
(S0C1 can be a symptom for that kind of error), when LE error handler is
not able to cope with
program errors (maybe LE control blocks are damaged too). If you are lucky,
you get a message like "backward chain destroyed" etc., but when you're in
a real mess, you will be thrown back to SYSUDUMP. IMO it is still necessary
for every developer to be able to read SYSUDUMPs or to have a person
nearby that is able to assist.
I do classes on dump diagnose, BTW, and not every developer needs to know
all about this, but he or she should have a fellow worker around who is
able
to help, just in case.
<ad>If someone in Germany or Middle Europe needs such classes,
please feel free to contact me offline.</ad>
Thank you, kind regards
Bernd
Am 25.11.2014 20:56, schrieb Peter Ten Eyck:
Thanks for the good feedback. I had the programmer use the SYSUDUMP DD for this
program... which did produce a SOC1 dump. This dump was sent to Abend-Aid and
the programmer was able to make a correction to the code and get the program
running cleanly.
I still do not know what it is about that program that would not produce a
CEEDUMP. As mentioned in my previous post, the identical compile and LE runtime
will produce a CEEDUMP for other failing programs. I wrote a simple COBOL
program (divide by zero… S0CB) to prove this.
----------------------------------------------------------------------
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
