>To help search engines: ABO = Automatic Binary Optimizer >>We haven't set off down the yellow-brick ABO road, so it's hard to gauge h= >>ow much angst we'll actually have to overcome. I'm pretty sure it won't be = >>trivial.
>I haven't seen ABO in action yet. Is there a listing that relates the instr >uctions after the optimization to the source statement? I suspect, there is >n't. Is LE still able to tell the statement where the problem occurred? How > would one find the source statement that cause the the problem to occur? >I'm often involved in cases where I have to work with machine readable dumps. There is a new listing when a program is processed by ABO, and this listing is used by IBM Fault Analyzer, but it is not used by LE. For CEEDUMP, you would manually map the offset to the line number. Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
