I have a medium-sized C++ application under development (conventional
batch). I have gotten fairly used to and fairly fond of debugging S0C4's and
the like with the LE CEEDUMP (which pinpoints that sort of error down to the
source code file and line number).
Suddenly -- and I can't quite define "suddenly" ("I didn't change anything")
-- ABENDs have started instead producing a Transaction Dump, which I find
much less convenient, especially since at the moment Dallas has IPCS hosed
up and unusable on our machine. (If I code a SYSUDUMP DD I also get one of
those, which is even less convenient for higher level language problems.)
Why would LE start issuing Transaction Dumps rather than CEEDUMPs? There are
no TRAP(OFF) or anything similar in the source code or in the LE runtime
options. A CEEDUMP DD statement makes no difference. There is no ESTAE
issued by my code. How the heck do I get LE back to a CEEDUMP, or what the
heck should I be looking for?
z/OS V2R4
+CEE3798I ATTEMPTING TO TAKE A DUMP FOR ABEND U4087 TO DATA SET:
blah.blah.blah
IGD100I 03DE ALLOCATED TO DDNAME SYS00003 DATACLAS ( )
IEA822I COMPLETE TRANSACTION DUMP WRITTEN TO blah.blah.blah
+CEE3797I LANGUAGE ENVIRONMENT HAS DYNAMICALLY CREATED A DUMP.
+CEE0374C CONDITION=CEE3204S TOKEN=00030C84 59C3C5C5 00000000 455
WHILE RUNNING PROGRAM myprogrm
AT THE TIME OF INTERRUPT
PSW 078D1400 9AE4AC66
GPR 0-3 FFFFFD09 FFFFFD09 1B5D522C 1AE4ABF2
GPR 4-7 1AE4ACF0 1AE541C0 1AE541C0 1AE541D3
GPR 8-B 1B584878 00000008 1B5BD2AC 1B5E68D0
GPR C-F 1B5771D8 1B584A58 1B5F1FAD 1B584A28
Charles
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
