Hopefully I remember it, since it's got my name all over it. :)
It's too bad it took so long to track down, but this is the kind
of C++ library bug that could cause all sorts of silent errors.
A test case that exercises the code can be vital to figuring it
out. You did us all a service by working with IBM to get it 
fixed. Thanks!



In article <[email protected]> you wrote:
> Anyone besides me remember this?

> I did report it to IBM, and I have been running SLIPs and dumps off and on
> for the past five+ months for LE Level two. They have now figured it out!

> https://www-304.ibm.com/support/entdocview.wss?uid=isg1PM68947  

> Charles
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
> Of Don Poitras
> Sent: Wednesday, February 01, 2012 10:25 AM
> To: [email protected]
> Subject: Re: S0C4 in CEE3DMP

> Then you should open a PMR with IBM. They have two problems to solve:

> 1. An abend in CEE3DMP
> 2. Incorrect diagnotic message 


> In article <[email protected]> you wrote:
> > It's not blowing up in SignalHandler.C; it is blowing up IN CEE3DMP: I get
> > half of the CEE3DMP output and no "I'm all done" message.

> > Charles

> > -----Original Message-----
> > From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf
> > Of Don Poitras
> > Sent: Tuesday, January 31, 2012 8:18 PM
> > To: [email protected]
> > Subject: Re: S0C4 in CEE3DMP

> > Tea leaves are good for making tea. :) I would compile SignalHandler.C
> with
> > the LIST option to see the psuedo assembly output and see from the dump
> > where the abend occured and try to figure out what went wrong. The message
> > you've given wouldn't lead me to think there was a problem in CEEDMP, but
> > rather in the calling code.

-- 
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
[email protected]           (919) 531-5637                Cary, NC 27513

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to