Re: AW: How does ABO report its outcome? (was: Migrating Cobol)

2017-03-29 Thread Tom Marchant
On Tue, 28 Mar 2017 21:31:11 +0200, Peter Hunkeler wrote:

>
>>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.
>
>So what you're saying is that an optional chargeable product knows how to 
>handle problems with ABO optimized code, but the standard runtime 
>environment does not? Really? What is the rationale behind?

What he is saying is that there is an optional chargeable product that will 
help you to analyze abends in your code. The information is available for 
you to analyze the dump yourself. This is the same as without ABO.

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: AW: How does ABO report its outcome? (was: Migrating Cobol)

2017-03-28 Thread Bill Woodger
Without any TEST option on the compile, LE gives you nothing but the offset of 
the failing instruction, then you find it in the compile listing. ABO gets you 
a new listing of the new code, a new place to consult for the offset.

If you compile with TEST options, the code generated for those options still 
exists in the ABO'd program, and if from the original program that results in 
additional information in the LE dump, then it will still do so after the 
program has been ABO'd.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


AW: How does ABO report its outcome? (was: Migrating Cobol)

2017-03-28 Thread Peter Hunkeler

>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.




So what you're saying is that an optional chargeable product knows how to 
handle problems with ABO optimized code, but the standard runtime environment 
does not? Really? What is the rationale behind?


--
Peter Hunkeler



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN