I don't have PDS unfortunately.
Sheesh! Mixed versions is a likely problem but IBM doesn't put any kind of
version tag in the libraries? Sheesh! Isn't there another way?
When the dump fails it makes it quite a way through, which leads me to
believe it is perhaps some sort of problem within the dump, not in invoking
the dump, but I don't really know.
I do NOT get CEE3846I CEEDUMP Processing completed.
The last line of the dump is
Local Variables:
eventCode enum EventTypes EventModify
this-> class Fields
******************************* BOTTOM OF DATA **************
And again, storage should not *in general* be hosed up despite the original
error. The initial error is intentional as a test of my signal handling
code. The *original* failing instructions are
char *oops = NULL;
*oops = 0; // should S0c4
Quite intentional. CEE3DMP has no trouble with oops.
%BLOCK39:>oops unsigned char * 0x0
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Ed Finnell
Sent: Tuesday, January 31, 2012 2:29 PM
To: [email protected]
Subject: Re: S0C4 in CEE3DMP
PDS has a nice HIST command. If you can get to the Trace table see which
modules it percolated thru.
In a message dated 1/31/2012 4:20:45 P.M. Central Standard Time,
[email protected] writes:
version of CEE.SCEERUN & RUN2?
----------------------------------------------------------------------
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
